Skip to content

[19.0][MIG] account_invoice_date_due: Migration to 19.0#2282

Open
gdgellatly wants to merge 21 commits intoOCA:19.0from
gdgellatly:19.0-mig-account_invoice_date_due
Open

[19.0][MIG] account_invoice_date_due: Migration to 19.0#2282
gdgellatly wants to merge 21 commits intoOCA:19.0from
gdgellatly:19.0-mig-account_invoice_date_due

Conversation

@gdgellatly
Copy link

@gdgellatly gdgellatly commented Feb 28, 2026

Summary

Migration of account_invoice_date_due module to 19.0.

  • Version bump to 19.0.1.0.0
  • Fixed groups_id -> group_ids rename in tests (v19 breaking change)

Test plan

  • Module installs successfully
  • Tests pass with --test-enable (3/3 tests pass)

luistorresm and others added 21 commits February 28, 2026 20:58
Allow update the date due in an invoice (Even if it's done). To avoid
cancel the invoice and generate again
This applies pending comments on OCA#632, which are:
- Fix some typos
- Be consistent with the license, use AGPL-3
- Add maintainer (not commented)
- Set group data as noupdate (not commented)
Don't use the wizard, but make the invoice_date_due editable for a specific group
Still, propagate the change to the invoice lines
Add tests

TT28875
- Include context keys for avoiding mail operations overhead.
The write method failed with a singleton error when updating a batch
of records.
This was caused by accessing `self.state` on the entire recordset.

The logic is now fixed to first filter for `posted` moves, and then
apply the due date propagation only to that safe subset. This ensures
batch operations no longer crash.
@gdgellatly gdgellatly force-pushed the 19.0-mig-account_invoice_date_due branch from 608319b to 9067af4 Compare February 28, 2026 21:11
Copy link

@dannyadair dannyadair left a comment

Choose a reason for hiding this comment

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

Still 18.0 references in

  • README.rst
  • static/description/index.html
  • i18n/account_invoice_date_due.pot

Otherwise code and functionality LGTM!

@gdgellatly gdgellatly marked this pull request as ready for review March 3, 2026 04:08
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.