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

When creating category, select all groups by default #20691

Closed
Hlavtox opened this issue Aug 24, 2020 · 4 comments · Fixed by #24403 or #27770
Closed

When creating category, select all groups by default #20691

Hlavtox opened this issue Aug 24, 2020 · 4 comments · Fixed by #24403 or #27770
Labels
BO Category: Back Office Categories Label: Which BO under menu is concerned Fixed Resolution: issue closed because fixed Good first issue Community: beginner-friendly issues Improvement Type: Improvement PM ✔️ Status: check done, behavior approved PR available Solution: issue is being addressed
Milestone

Comments

@Hlavtox
Copy link
Contributor

Hlavtox commented Aug 24, 2020

Is your feature request related to a problem?

When me or an employee is creating a category, we often forget to check our extra customer groups. Then a customer is complaining that he cannot enter some specific category.

Describe the solution you'd like

When creating new category, select all customer groups by default, not just the 3 original ones.

Additional context

I think that customer groups are used mostly to set special prices for good customers, that buy in bulk, rather then to restrict access to some categories, so it will please majority of users.

@prestashop-issue-bot
Copy link

Thanks for opening this issue! We will help you to keep its state consistent

@khouloudbelguith
Copy link
Contributor

Hi @Hlavtox,

Thanks for your report.
Ping @PrestaShop/prestashop-product-team what do you think?

Thanks!

@khouloudbelguith khouloudbelguith added BO Category: Back Office Categories Label: Which BO under menu is concerned Improvement Type: Improvement Needs Specs Status: issue needs to be specified Waiting for PM Status: action required, waiting for product feedback labels Aug 24, 2020
@LouiseBonnard
Copy link
Contributor

I agree with @Hlavtox, all groups should be ticked by default. I've made a brief search and it seems to be the only page where it is forgotten along with the customer creation form in the Customers section of the back office but the use case is not the same so here is my recommendation:

  1. tick by default all customers groups in the Catalog > Categories > Add new category page
  2. tick by default only the Customer group in the Customers > Customers > Add new customer page - none if the store has no Customer group anymore

@LouiseBonnard LouiseBonnard added Good first issue Community: beginner-friendly issues PM ✔️ Status: check done, behavior approved Ready Status: Issue is ready to be worked on and removed Needs Specs Status: issue needs to be specified Waiting for PM Status: action required, waiting for product feedback labels Aug 27, 2020
@hibatallahAouadni hibatallahAouadni added the PR available Solution: issue is being addressed label May 26, 2021
@khouloudbelguith khouloudbelguith added the Fixed Resolution: issue closed because fixed label Dec 13, 2021
@prestashop-issue-bot prestashop-issue-bot bot removed the Ready Status: Issue is ready to be worked on label Dec 13, 2021
@khouloudbelguith khouloudbelguith added this to the 8.0.0 milestone Dec 13, 2021
@khouloudbelguith khouloudbelguith added this to Not ready in PrestaShop 8.0.0 via automation Dec 13, 2021
@khouloudbelguith khouloudbelguith moved this from Not ready to To be merged in PrestaShop 8.0.0 Dec 13, 2021
@prestashop-issue-bot prestashop-issue-bot bot added WIP Status: Work In Progress and removed Fixed Resolution: issue closed because fixed labels Dec 13, 2021
PrestaShop 8.0.0 automation moved this from To be merged to Done Dec 17, 2021
@prestashop-issue-bot prestashop-issue-bot bot added Fixed Resolution: issue closed because fixed and removed WIP Status: Work In Progress labels Dec 17, 2021
@jolelievre
Copy link
Contributor

I reopen this issue because the solution suggested for Webservice to use Symfony is not adapted
So I created this PR #27770 which reverts the use of Symfony

But it should also of course work as expected with the previous fix

@jolelievre jolelievre reopened this Feb 22, 2022
@prestashop-issue-bot prestashop-issue-bot bot removed the Fixed Resolution: issue closed because fixed label Feb 22, 2022
@jolelievre jolelievre moved this from Done to To be reviewed in PrestaShop 8.0.0 Feb 23, 2022
@prestashop-issue-bot prestashop-issue-bot bot added the WIP Status: Work In Progress label Feb 23, 2022
@khouloudbelguith khouloudbelguith moved this from To be reviewed to To be merged in PrestaShop 8.0.0 Mar 24, 2022
@prestashop-issue-bot prestashop-issue-bot bot removed the WIP Status: Work In Progress label Mar 24, 2022
PrestaShop 8.0.0 automation moved this from To be merged to Done Mar 24, 2022
@prestashop-issue-bot prestashop-issue-bot bot added the Fixed Resolution: issue closed because fixed label Mar 24, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
BO Category: Back Office Categories Label: Which BO under menu is concerned Fixed Resolution: issue closed because fixed Good first issue Community: beginner-friendly issues Improvement Type: Improvement PM ✔️ Status: check done, behavior approved PR available Solution: issue is being addressed
Projects
No open projects
5 participants