Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[16.0][MIG] kpi: Migration to 16.0 #920

Open
wants to merge 27 commits into
base: 16.0
Choose a base branch
from

Conversation

matiasperalta1
Copy link
Contributor

No description provided.

naousse and others added 26 commits August 19, 2024 15:08
* kpi migration to odoo 9
* UI error connected
* Correction base on last maxime review
* correction on @elicoidal review
* Warning exception improve in kpi_threshold
* Latest Ellicoidal comment implemented
* last Ellicoial recommendation done.
* Copyright corrected
Currently translated at 100.0% (68 of 68 strings)

Translation: reporting-engine-12.0/reporting-engine-12.0-kpi
Translate-URL: https://translation.odoo-community.org/projects/reporting-engine-12-0/reporting-engine-12-0-kpi/pt_BR/
Updated by "Update PO files to match POT (msgmerge)" hook in Weblate.

Translation: reporting-engine-12.0/reporting-engine-12.0-kpi
Translate-URL: https://translation.odoo-community.org/projects/reporting-engine-12-0/reporting-engine-12-0-kpi/
Currently translated at 100.0% (79 of 79 strings)

Translation: reporting-engine-12.0/reporting-engine-12.0-kpi
Translate-URL: https://translation.odoo-community.org/projects/reporting-engine-12-0/reporting-engine-12-0-kpi/pt_BR/
kpi_type = fields.Selection(
[
("python", "Python"),
("local", "SQL - Local DB"),

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

according L122 this must be 'local' --> 'sql'

[
("python", "Python"),
("local", "SQL - Local DB"),
("external", "SQL - External DB"),

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

remove


next_execution_date = fields.Datetime(readonly=True)
value = fields.Float(compute="_compute_display_last_kpi_value")
color = fields.Text(compute="_compute_display_last_kpi_value")

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

because we're removing threshold to simplify the module, color should not exist

<field name="next_execution_date" colspan="3" />
<separator string="KPI Computation" colspan="6" />
<newline />
<field name="kpi_type" colspan="2" />
Copy link

@jok-adhoc jok-adhoc Sep 9, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It would be better to have colspan equal to "6" in order to have both kpi_type and kpi_code one bellow the other. Another option could be creating two diff groups

With colspan = "2" , the code's label is in the same line as kpi_type and the editable field bellow, what makes the label confusing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.