[18.0][MIG] project_forecast_line: Migration to 18.0#1692
[18.0][MIG] project_forecast_line: Migration to 18.0#1692solomonprabu wants to merge 79 commits intoOCA:18.0from
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
|
Test are failing, review the use of flush_model in tests. |
Tests are succeeding now! |
Nice, can you squash the commits into a single migration commit? Or, if you prefer, keep one migration commit and one improvement commit. I see too many commits, let’s keep the commit history simple. |
|
Can you take a look at these comments here and apply them when necessary #1247 |
Looking into it, will let you know once it is fixed. |
I totally agree with you on this! will squash the commits once I'm done. |
|
Regarding this, I had the same opinion on this. For now I do not see any complications on using the fields from This could be time consuming though, if something falls apart! |
|
@tarteo Also using the field from |
|
@tarteo I have tested the files locally after replacing the fields from |
tarteo
left a comment
There was a problem hiding this comment.
@solomonprabu Thanks for the fixes! The date fields can also be addressed later, it is out of scope for this migration PR.
IMO the ideal situation would be:
- A module
project_datethat just introduces the fields project_timelinedepends onproject_date(reusing those fields instead of adding new ones)project_forecast_linedepends onproject_date(reusing those fields instead of adding new ones)
This way we avoid introducing a dependency on web_timeline, while still having any task planned using the forecast module reflected in the the project task timeline view.
@tarteo 🙌 Cheers for the PR approval and have a good weekend :) |
8ba64ac to
8ac84f3
Compare
|
@tarteo The issue is in here, the But that makes the |
|
@tarteo The bug is now fixed! |
|
@luisDIXMIT All checks have passed. |
|
Nice, but could you squash the commits? It's too large. It should be squashed into a single migration commit, or perhaps into two commits if there are fixes or improvements outside the migration scope. |
[FIX] Demo data xml to fix installation errors and warnings [FIX] Demo data xml to fix installation errors and warnings [FIX] Typo [FIX] Typo [FIX] Demo data xml to fix installation errors and warnings [FIX] fixed test case error, mis-calculations and xml errors [ADD] Improved test coverage and improved onchange method [FIX] Demo data xml to fix installation errors and warnings [FIX] Typo [FIX] fixed test case error, mis-calculations and xml errors [FIX] Pre commit errors [UPDATE] updated missing variable [UPDATE] updated missing variables [FIX] Typo [FIX] implemented feedbacks from PR OCA#1247 [UPDATE] Introduced new test case [DEL] removed duplicate code [FIX] reverting field changes to fix tests [UPDATE] Changing logger warning to info. To maintain clean logs and for pipeline to succeed, as warnings in log stops the container from succeeding [ADD] Added new testcases to improve code coverage [FIX] incorrect date object [UPDATE] fixing test method [ADD] Added test cases and refactored tests [FIX] fixing parameters [ADD] Hr Leave test coverage [FIX] Pre commit fix [FIX] logger warning to info [Add] Code coverage improvement [Add] Code coverage improvement for Hr Leave [UPDATE] Update _write method with _write_multi. Odoo18 changes
e92d97e to
8c5860a
Compare
Squashed! Ready to merge? |
luisDIXMIT
left a comment
There was a problem hiding this comment.
Code review, good work, some minor comments.
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! |






[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.