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

[RFC] product_assortment : select model applicability #1991

Closed
francesco-ooops opened this issue Apr 22, 2022 · 1 comment
Closed

[RFC] product_assortment : select model applicability #1991

francesco-ooops opened this issue Apr 22, 2022 · 1 comment
Labels
enhancement stale PR/Issue without recent activity, it'll be soon closed automatically.

Comments

@francesco-ooops
Copy link
Contributor

Hi, we're planning to port to 14 several assortment modules:

website_sale_product_assortment (once it will be ready)
stock_picking_product_assortment
product_pricelist_assortment
sale_order_product_assortment

While doing this, we realized that:

  • once there will be many assortments records in a db, it can become difficult to keep track what is the purpose of each assortment (was it created for website? for stock picking? for sales?)
  • every assortment created applies automatically to every context, so there isn't the possibility to define case: "Customer 1 can purchase products 1, 2, 3 on website, while on SO they can purchase products 1, 2, 3, 4, 5"

The idea is to add an applicability flag (eg: "apply to sales", "apply to website") to each module extending product_assortment to be displayed in the assortment form, in order to be able to decide where to use or not a certain assortment.

How do you suggest to proceed with this? add this change directly to migrations to 14, since none of these modules are migrated (therefore in use)? or do you suggest another approach?

tagging contributors for comments, @rousseldenis @CarlosRoca13 @pedrobaeza :)

Copy link

There hasn't been any activity on this issue in the past 6 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 issue 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 Apr 21, 2024
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale May 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement stale PR/Issue without recent activity, it'll be soon closed automatically.
Projects
None yet
Development

No branches or pull requests

1 participant