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

[18.0][MIG] stock_no_negative: Migration to 18.0 #1830

Open
wants to merge 2 commits into
base: 18.0
Choose a base branch
from

Conversation

woutswennen
Copy link

Oca module didnt work as we where not able to sellect the allow_negative_stock field on product

@@ -11,7 +11,7 @@
<field name="inherit_id" ref="stock.view_template_property_form" />
<field name="arch" type="xml">
<field name="categ_id" position="after">
<field name="allow_negative_stock" invisible="type != 'product'" />
<field name="allow_negative_stock" invisible="type == 'service'" />
Copy link
Member

Choose a reason for hiding this comment

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

not is_storable, I think. See odoo/odoo@728d9f83f6d14

Copy link
Member

Choose a reason for hiding this comment

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

Also, might be a nice improvement to move the field until after is_storable itself.
image

@woutswennen woutswennen force-pushed the 18.0-mig-stock_no_negative branch from 9bfe541 to 69bdcdf Compare February 26, 2025 10:26
@rousseldenis
Copy link
Contributor

/ocabot migration stock_no_negative

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.

@woutswennen You should follow migration guide here: https://github.com/OCA/maintainer-tools/wiki/Migration-to-version-18.0#technical-method-to-migrate-a-module-from-170-to-180-branch

Especially, you should keep commits history.

Thanks

@StefanRijnhart
Copy link
Member

Wait, this is not the migration, it's a fix of the migration. @woutswennen Please update commit message and PR name accordingly.

@StefanRijnhart
Copy link
Member

Also, duplicate of #1766

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants