[18.0][MIG] project_forecast_line: Migration to 18.0#1692
Conversation
in some cases, we could have capacity consumed by a task which was not matching a work capacity line in the period because of a faulty optimisation we were making which skipped the creation of lines with a capacity of 0 -> then we had no line on which to compute the negative consolidated capacity. We remove the optimisation to fix this case and show the problematic periods in the consolidated capacity graphs
Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Translation: project-15.0/project-15.0-project_forecast_line Translate-URL: https://translation.odoo-community.org/projects/project-15-0/project-15-0-project_forecast_line/
During some operations, forecast lines are deleted and recreated. This can lead to some hr.employee.forecast.role lines being deleted which leaves the forecast lines on the same period without a related document to store the consolidated capacity. Normally that line is recreated shortly afterwards but the creation does not recompute the link between the parent-less lines and the new one. This patches forces the recomputation when new lines are created.
…tion states" This reverts commit 82f5f36.
The idea is to have two consolidated forecast fields, instead of setting.
Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Translation: project-15.0/project-15.0-project_forecast_line Translate-URL: https://translation.odoo-community.org/projects/project-15-0/project-15-0-project_forecast_line/
Add computed fields to written fields to trigger forecast lines update
Add hook for several UoM hours/days conversion
…oyee is not active
luisDIXMIT
left a comment
There was a problem hiding this comment.
Good work, LGTM, I won't block the PR.
|
This PR has the |
|
@sebastienbeau PR is ready to be merged! |
Based on OCA#1692 for 18.0; manually bumped and sanity-checked for 19.0.
Based on OCA#1692 for 18.0; manually bumped and sanity-checked for 19.0.
Based on OCA#1692 for 18.0; manually bumped and sanity-checked for 19.0.
Based on OCA#1692 for 18.0; manually bumped and sanity-checked for 19.0.
Based on OCA#1692 for 18.0; manually bumped and sanity-checked for 19.0.
Based on OCA#1692 for 18.0; manually bumped and sanity-checked for 19.0.
Based on OCA#1692 for 18.0; manually bumped and sanity-checked for 19.0.
|
@AaronHForgeFlow PR merge is still pending. |
|
@rafaelbn Could you please merge this. |
BhaveshHeliconia
left a comment
There was a problem hiding this comment.
Please squash the commits as explained here: https://github.com/OCA/maintainer-tools/wiki/Merge-commits-in-pull-requests#mergesquash-the-commits-generated-by-bots-or-weblate
39750cc to
746255c
Compare
Hi, I have squashed my commits. |
|
/ocabot migration project_forecast_line |
|
/ocabot merge nobump |
|
Hey, thanks for contributing! Proceeding to merge this for you. |
|
Congratulations, your PR was merged at 2a42fdb. Thanks a lot for contributing to OCA. ❤️ |
[Migrated]
project_forecast_lineto Odoo 18.0.Note on Views:
I kept the inheritance targeting
project.project_project_stage_view_tree. Even though Odoo 18 is moving toward_view_listnaming, the base project module still uses the_view_treeID for this record, so I've used that to avoid any reference errors.