Skip to content

[20.0][MIG] base_tier_validation_forward: Migration to 20.0 - #100

Open
Pani-k-folk wants to merge 43 commits into
OCA:20.0from
ecosoft-odoo:20.0-mig-base_tier_validation_forward
Open

Pani-k-folk wants to merge 43 commits into
OCA:20.0from
ecosoft-odoo:20.0-mig-base_tier_validation_forward

Conversation

@Pani-k-folk

@Pani-k-folk Pani-k-folk commented Oct 14, 2026 •

Copy link
Copy Markdown

Depends on: #94

Changes

  • Version bumped to 20.0.1.0.0.
  • Security: ir.model.access is replaced by ir.access in 20.0. Converted security/ir.model.access.csv to security/ir.access.csv, same xmlid and permissions (crud for internal users on the forward wizard).
  • Icons: in 20.0 the button icon attribute takes a Material Symbols name (Font Awesome is not loaded in the backend): fa-arrow-circle-right → arrow_circle_right on the Forward button.
  • Fields on tier.review: 20.0 warns is both compute and related for review_type, reviewer_id, reviewer_group_id, has_comment and approve_sequence, which fails the checklog-odoo CI step. On 19.0, Odoo already used related and ignored compute for these fields, so I removed the unused compute= and the matching lines in _compute_definition_data. Behaviour does not change: they stay stored related fields, and forwarded reviews keep the values the wizard writes.
  • Lint: pre-commit auto fixes (XML headers, ruff format) in their own commit.

Notes

AI disclosure

Assisted-by: Claude Opus 5.5 (migration changes were reviewed and tested by me)

kittiu and others added 30 commits October 14, 2026 14:43
Currently translated at 100.0% (35 of 35 strings)

Translation: server-ux-16.0/server-ux-16.0-base_tier_validation_forward
Translate-URL: https://translation.odoo-community.org/projects/server-ux-16-0/server-ux-16-0-base_tier_validation_forward/es/
Currently translated at 100.0% (34 of 34 strings)

Translation: server-ux-17.0/server-ux-17.0-base_tier_validation_forward
Translate-URL: https://translation.odoo-community.org/projects/server-ux-17-0/server-ux-17-0-base_tier_validation_forward/it/
Currently translated at 100.0% (35 of 35 strings)

Translation: server-ux-17.0/server-ux-17.0-base_tier_validation_forward
Translate-URL: https://translation.odoo-community.org/projects/server-ux-17-0/server-ux-17-0-base_tier_validation_forward/it/
Currently translated at 100.0% (35 of 35 strings)

Translation: server-ux-18.0/server-ux-18.0-base_tier_validation_forward
Translate-URL: https://translation.odoo-community.org/projects/server-ux-18-0/server-ux-18-0-base_tier_validation_forward/nl_NL/
By ordering only by sequence, the order is not deterministic when there are
forwards, because the forwards are created with the same sequence as the
forwarded reviews.
StefanRijnhart and others added 13 commits October 14, 2026 14:43
… after forward

How to reproduce:

* Create two reviews for the same model with different sequences and `Approve by
sequence` enabled.
* Request validation on a record. Let the user of the first review forward the
first validation.

Desired result:

The new (forward) review is in state 'pending', and the remaining review is in
state 'waiting'.

Actual result:

Both the new (forward) review and the remaining review are in state 'pending'.

Suggested solution:

_compute_can_review has to be deferred during the fowarding process. It was
called explicitely afterwards already.
Currently translated at 100.0% (35 of 35 strings)

Translation: tier-validation-19.0/tier-validation-19.0-base_tier_validation_forward
Translate-URL: https://translation.odoo-community.org/projects/tier-validation-19-0/tier-validation-19-0-base_tier_validation_forward/nl/
Currently translated at 2.8% (1 of 35 strings)

Translation: tier-validation-19.0/tier-validation-19.0-base_tier_validation_forward
Translate-URL: https://translation.odoo-community.org/projects/tier-validation-19-0/tier-validation-19-0-base_tier_validation_forward/fr/
The Forward button had no margin, so it touched the Reject button on the
validation banner. Give it the same gap as between Validate and Reject.
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.