Skip to content
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] [MIG] stock_location_children #1802

Conversation

aiendry-aktivsoftware
Copy link

Standard migration to version 16.0

grindtildeath and others added 17 commits July 25, 2023 16:22
* Any child_ids changed on a children_ids should recompute locations:
  otherwise only 2 levels are updated.
* Flush any change in the hierarchy before executing the SQL
When other modules add locations in "stock.stock_location_stock", the
assertions miss them. Create a new tree of locations to run the tests.
Currently translated at 100.0% (6 of 6 strings)

Translation: stock-logistics-warehouse-14.0/stock-logistics-warehouse-14.0-stock_location_children
Translate-URL: https://translation.odoo-community.org/projects/stock-logistics-warehouse-14-0/stock-logistics-warehouse-14-0-stock_location_children/it/
Currently translated at 100.0% (6 of 6 strings)

Translation: stock-logistics-warehouse-14.0/stock-logistics-warehouse-14.0-stock_location_children
Translate-URL: https://translation.odoo-community.org/projects/stock-logistics-warehouse-14-0/stock-logistics-warehouse-14-0-stock_location_children/it/
Currently translated at 100.0% (6 of 6 strings)

Translation: stock-logistics-warehouse-14.0/stock-logistics-warehouse-14.0-stock_location_children
Translate-URL: https://translation.odoo-community.org/projects/stock-logistics-warehouse-14-0/stock-logistics-warehouse-14-0-stock_location_children/it/
@rousseldenis
Copy link
Contributor

/ocabot migration stock_location_children

Copy link
Contributor

@rousseldenis rousseldenis left a comment

Choose a reason for hiding this comment

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

Code review

Copy link

There hasn't been any activity on this pull request in the past 4 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days.
If you want this PR to never become stale, please ask a PSC member to apply the "no stale" label.

@github-actions github-actions bot added the stale PR/Issue without recent activity, it'll be soon closed automatically. label Mar 17, 2024
@github-actions github-actions bot closed this Apr 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
migration needs review stale PR/Issue without recent activity, it'll be soon closed automatically.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

9 participants