-
Notifications
You must be signed in to change notification settings - Fork 2
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] [REF] [MIG] coopiteasy_custom #106
base: 16.0
Are you sure you want to change the base?
Conversation
b3f2246
to
835732a
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
❗ Your organization needs to install the Codecov GitHub app to enable full functionality. Additional details and impacted files@@ Coverage Diff @@
## 16.0 #106 +/- ##
==========================================
+ Coverage 87.80% 88.37% +0.56%
==========================================
Files 6 9 +3
Lines 123 129 +6
Branches 15 15
==========================================
+ Hits 108 114 +6
Misses 9 9
Partials 6 6 ☔ View full report in Codecov by Sentry. |
1e9a96e
to
75d3f12
Compare
@victor-champonnois Ok to not porting |
adaeab3
to
60d654e
Compare
@robinkeunen OK, I remove it then, thanks |
TODO : test the script to migrate linked_tasks to dependent tasks |
migration script needed for PR field |
Maybe a helpful comment, but I wonder how migration scripts will work in this scenario. I envision the following execution flow:
|
for task in env["project.task"].search([]): | ||
if task.link_task_ids: | ||
task.project_id.allow_task_dependencies = True | ||
task.write({"depend_on_ids": task.link_task_ids}) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@remytms will this work ? The field is not defined anymore un the module at execution time.
60d654e
to
f6207d3
Compare
@huguesdk @remytms @victor-champonnois Can I get some review please 🙏 |
f6207d3
to
35fee29
Compare
[ADD] cie_custom: uri and priority fields Signed-off-by: Carmen Bianca Bakker <[email protected]>
…time sheets Signed-off-by: Carmen Bianca Bakker <[email protected]>
Signed-off-by: Carmen Bianca Bakker <[email protected]>
blacken coopiteasy custom wip Signed-off-by: Carmen Bianca Bakker <[email protected]>
Signed-off-by: Carmen Bianca Bakker <[email protected]>
Signed-off-by: Carmen Bianca Bakker <[email protected]>
Signed-off-by: Carmen Bianca Bakker <[email protected]>
Signed-off-by: Carmen Bianca Bakker <[email protected]>
Signed-off-by: Carmen Bianca Bakker <[email protected]>
Signed-off-by: Carmen Bianca Bakker <[email protected]>
Signed-off-by: Carmen Bianca Bakker <[email protected]>
limit timesheet activity projects selection to open projects.
move analytic account custom order logic to project. previously (in odoo 9), timesheet lines where directly linked to analytic accounts. now (in odoo 12), they are linked to projects.
limit timesheet activity projects selection to open projects in task timesheets and timesheet sheet details.
Signed-off-by: Carmen Bianca Bakker <[email protected]>
Signed-off-by: Carmen Bianca Bakker <[email protected]>
allow to directly select a task (from open projects only) in a timesheet line without selecting a project first.
abandon other functionalities
35fee29
to
63cf94c
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm, one comment
@openupgrade.migrate() | ||
def migrate(env, version): | ||
env.cr.execute( | ||
""" | ||
alter table project_task drop column if exists reviewer_id; | ||
alter table project_task drop column if exists tester_id; | ||
alter table project_task drop column if exists int_priority; | ||
drop table link_task_relation_table; | ||
""" | ||
) | ||
env.cr.commit() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this is typically not done in oca projects, preferring to keep (dead) data. here we may not care because we're the only user?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes, i think we can clean it up : these fields were very sparsely used, the data in it is not relevant.
This PR has the |
cf internal discussion : https://docs.google.com/spreadsheets/d/1Bcyhw0BJRztjKtIGJmnnpBXLGv5Ctb7l378MqoyjgFQ/edit#gid=2001558567
Note : I didn't make a PR to 12 because it is useless. This refactoring is only due to the migration because we want to reduce the codebase.
@carmenbianca I am not sure if I should write a script to rename the cron's XML IDs. Do you have an opinion ?(not nessary anymore)@robinkeunen I am really wondering whether it is worth it to continue using "sort_project_by_timesheet_line_count". Without this module, with Odoo standard, we can order the projects via total_timesheet_time or by task_count (just by configuring the DB via the interface). This module seems a bit complex to me compared to the functionality it provides.
If we don't want to use 'in interface' configuration because it could get lost in future migration, we could just set the model's order to total_timesheet_time or task_count in a module, without the need to compute "recent_timesheet_line_count".
What do you think ?
task : https://gestion.coopiteasy.be/web#id=10959&action=475&active_id=492&model=project.task&view_type=form&menu_id=