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

Add new filter "product type" to section where we can add products to a category #28885

Open
Eddcapone opened this issue Jun 25, 2020 · 6 comments · May be fixed by #29366
Open

Add new filter "product type" to section where we can add products to a category #28885

Eddcapone opened this issue Jun 25, 2020 · 6 comments · May be fixed by #29366
Labels
Component: Filter feature request Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development Priority: P4 No current plan to fix. Fixing can be deferred as a logical part of more important work. Progress: PR in progress Reported on 2.4.0 Indicates original Magento version for the Issue report. Reproduced on 2.4.x The issue has been reproduced on latest 2.4-develop branch Severity: S3 Affects non-critical data or functionality and does not force users to employ a workaround. Triage: Ready for Triage Issue is ready to me triaged with Product Manager

Comments

@Eddcapone
Copy link

Eddcapone commented Jun 25, 2020

Description (*)

Magento 2.4
I just added a new category and now I have to add products to it.
The products I need to add to the category, are configurable products and start with the name "Spannrahmen".

Problem: There are also thousands of simple products starting with "Spannrahmen", and so I can't find the configurable product fast enough, and it is extremly laborious task, because of all the unecessary data showing to me.

Expected behavior (*)

In a category page should be a filter for product type. If I could sort for product type, then it would be much easier, because then only the configurable products are showing.

Benefits

It would make the work much faster.

Additional information

It should be a must have for Enterprise...

@m2-assistant
Copy link

m2-assistant bot commented Jun 25, 2020

Hi @Eddcapone. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

  • Summary of the issue
  • Information on your environment
  • Steps to reproduce
  • Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento give me 2.4-develop instance - upcoming 2.4.x release

For more details, please, review the Magento Contributor Assistant documentation.

Please, add a comment to assign the issue: @magento I am working on this


@ghost ghost added this to Ready for QA in Community Backlog Jun 25, 2020
@magento-engcom-team magento-engcom-team added the Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed label Jun 25, 2020
@Eddcapone Eddcapone changed the title Add product type to filter of section where we can add products to a category Add new filter "product type" to section where we can add products to a category Jun 25, 2020
@engcom-Lima engcom-Lima self-assigned this Jun 30, 2020
@m2-assistant
Copy link

m2-assistant bot commented Jun 30, 2020

Hi @engcom-Lima. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

  • 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).

    DetailsIf the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

  • 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

  • 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

  • 4. Verify that the issue is reproducible on 2.4-develop branch

    Details- Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
    - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
    - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

  • 5. Add label Issue: Confirmed once verification is complete.

  • 6. Make sure that automatic system confirms that report has been added to the backlog.

@engcom-Lima engcom-Lima added Reproduced on 2.4.x The issue has been reproduced on latest 2.4-develop branch Component: Filter Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed labels Jun 30, 2020
@ghost ghost unassigned engcom-Lima Jun 30, 2020
@ghost ghost moved this from Ready for QA to Ready for Dev in Community Backlog Jun 30, 2020
@magento-engcom-team
Copy link
Contributor

✅ Confirmed by @engcom-Lima
Thank you for verifying the issue. Based on the provided information internal tickets MC-35567 were created

Issue Available: @engcom-Lima, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

@magento-engcom-team magento-engcom-team added the Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development label Jun 30, 2020
@engcom-Kilo engcom-Kilo self-assigned this Jul 31, 2020
@m2-assistant
Copy link

m2-assistant bot commented Jul 31, 2020

Hi @engcom-Kilo. Thank you for working on this issue.
Looks like this issue is already verified and confirmed. But if you want to validate it one more time, please, go though the following instruction:

    1. Add/Edit Component: XXXXX label(s) to the ticket, indicating the components it may be related to.
    1. Verify that the issue is reproducible on 2.4-develop branch
      Details- Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
      - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
      - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!
    1. If the issue is not relevant or is not reproducible any more, feel free to close it.

@ghost ghost moved this from Ready for Dev to Dev in Progress in Community Backlog Jul 31, 2020
@engcom-Kilo
Copy link
Contributor

I am working on this

@ghost ghost moved this from Dev in Progress to PR In Progress in Community Backlog Aug 3, 2020
@engcom-Alfa engcom-Alfa added Triage: Ready for Triage Issue is ready to me triaged with Product Manager Priority: P4 No current plan to fix. Fixing can be deferred as a logical part of more important work. Severity: S3 Affects non-critical data or functionality and does not force users to employ a workaround. labels Aug 10, 2020
@engcom-Hotel engcom-Hotel self-assigned this Aug 25, 2020
@m2-assistant
Copy link

m2-assistant bot commented Aug 25, 2020

Hi @engcom-Hotel. Thank you for working on this issue.
Looks like this issue is already verified and confirmed. But if you want to validate it one more time, please, go though the following instruction:

    1. Add/Edit Component: XXXXX label(s) to the ticket, indicating the components it may be related to.
    1. Verify that the issue is reproducible on 2.4-develop branch
      Details- Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
      - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
      - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!
    1. If the issue is not relevant or is not reproducible any more, feel free to close it.

@sidolov sidolov added this to Ready for Development in Low Priority Backlog Sep 24, 2020
@m2-community-project m2-community-project bot moved this from Ready for Development to Pull Request In Progress in Low Priority Backlog Sep 24, 2020
@m2-community-project m2-community-project bot added Progress: PR Created Indicates that Pull Request has been created to fix issue and removed Progress: PR in progress Progress: PR Created Indicates that Pull Request has been created to fix issue labels Sep 24, 2020
@ghost ghost unassigned engcom-Hotel Oct 8, 2020
@magento-engcom-team magento-engcom-team added the Reported on 2.4.0 Indicates original Magento version for the Issue report. label Nov 13, 2020
@m2-community-project m2-community-project bot added this to Pull Request in Progress in Feature Requests Backlog Nov 13, 2020
@m2-community-project m2-community-project bot removed this from PR In Progress in Community Backlog Nov 13, 2020
@m2-community-project m2-community-project bot removed this from Pull Request In Progress in Low Priority Backlog Nov 13, 2020
@engcom-Kilo engcom-Kilo removed their assignment Dec 2, 2020
@m2-community-project m2-community-project bot added Progress: PR in progress and removed Progress: PR Created Indicates that Pull Request has been created to fix issue labels Dec 2, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Component: Filter feature request Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development Priority: P4 No current plan to fix. Fixing can be deferred as a logical part of more important work. Progress: PR in progress Reported on 2.4.0 Indicates original Magento version for the Issue report. Reproduced on 2.4.x The issue has been reproduced on latest 2.4-develop branch Severity: S3 Affects non-critical data or functionality and does not force users to employ a workaround. Triage: Ready for Triage Issue is ready to me triaged with Product Manager
Projects
Feature Requests Backlog
  
Pull Request in Progress
Development

Successfully merging a pull request may close this issue.

6 participants