[19.0] [MIG] contract: Migration to 19.0#1312
Conversation
877c2f7 to
8f589c2
Compare
b18f362 to
885e5a6
Compare
|
@BhaveshHeliconia can you please handle the failing tests so we can push this forward? |
a38846e to
c99f54f
Compare
|
@BhaveshHeliconia could you please re-run the CI checks? |
c99f54f to
983c9c2
Compare
a653227 to
3251a90
Compare
|
/ocabot migration contract Please cherry-pick #1343 |
3251a90 to
a3218c0
Compare
@pedrobaeza : Done. Thanks! |
a3218c0 to
b57bad9
Compare
65801a9 to
4ce03c5
Compare
|
@pedrobaeza : I’ve completed all the changes you recommended. Thanks for the feedback! |
b527c46 to
4e377c2
Compare
|
Please include #1341 |
4e377c2 to
8cddba3
Compare
Done. Thanks! |
…ing onchanges When copying values from the contract template, skip assignment if the value is already the same on the contract. This prevents triggering unnecessary onchanges without altering the behavior.
…ct lines This field is unused in this module, but in the contract_sale_invoicing module it is used to search Sales Orders. However, many times this field goes unnoticed and users set the analytic distribution directly on the lines. After this commit, the field is computed automatically based on the contract lines.
… does not have access TT59505
On portal, the cancelled lines are not distinguished from running ones, as the next invoice date is still displayed, and the color is the same (on contrary than the backend, that appears greyed). So let's do something similar in portal: - Put the row as grey. - Hide the nexte invoice date on that case. TT59704
dd55d88 to
5923b16
Compare
|
@carlos-lopez-tecnativa thanks for the review. I’ve addressed your comments. |
|
Hello @sbidoul , @AaronHForgeFlow , sorry for pinging you directly, can you pls trigger merge here? |
carlos-lopez-tecnativa
left a comment
There was a problem hiding this comment.
In my previous comment, I suggested squashing the administrative commits for the same language and the same author, but I noticed that you squashed commits that should not have been squashed and merged them into the previous commit, losing the original author. Please review this and rework the Git history correctly.
You can read this documentation if it helps:
https://github.com/OCA/maintainer-tools/wiki/Merge-commits-in-pull-requests
| invoices |= self.env["account.move"].search( | ||
| [("old_contract_id", "=", self.ids)] | ||
| ) |
There was a problem hiding this comment.
There was a problem hiding this comment.
Additionally, if you pass a list of IDs, the operator should be in instead of =. Please clarify the reason for this change.
There was a problem hiding this comment.
Done. Changed to in to correctly handle NewId in Odoo 19. This fixes the incorrect count for new contracts and keeps the recurrence field editable. Thanks!
I squashed all translation-related commits together, but I understand now that some commits should have remained separate to preserve the original authorship. I'll rework the Git history accordingly and add it to my TODO list.
There was a problem hiding this comment.
Yes, you should only merge translation commits coming from the same author, not all the translations commits together.
5923b16 to
97c88f7
Compare


No description provided.