- Notifications
You must be signed in to change notification settings - Fork 9.4k
Closed
Labels
Area: APIsComponent: GraphQLGraphQLGraphQLIssue: ConfirmedGate 3 Passed. Manual verification of the issue completed. Issue is confirmedGate 3 Passed. Manual verification of the issue completed. Issue is confirmedPAPPartners acceleration programPartners acceleration programPriority: P1Once P0 defects have been fixed, a defect having this priority is the next candidate for fixing.Once P0 defects have been fixed, a defect having this priority is the next candidate for fixing.Progress: doneProject: GraphQLReproduced on 2.4.xThe issue has been reproduced on latest 2.4-develop branchThe issue has been reproduced on latest 2.4-develop branch
Description
Preconditions (*)
- Magento 2.4.1
- Two root categories exists in Admin-Categories
- Two stores exists with different root categories for each of it
- Each Stores should have atleast one store view.
- Each Root category should have one sub-category.
- Product should belong to both stores. i.e. Assign product to all root and sub categories.
Steps to reproduce (*)
- Query -
{ "store": "engchildren" } query { products(filter: { url_key: { eq: "gabrielle-micro-sleeve-top"} }){ items { categories { name id url_path breadcrumbs { category_id category_name category_level } } } } }
Expected result (*)
- Store specific data should be returned.
Actual result (*)
- Response -
{ "data": { "products": { "items": [ { "categories": [ { "name": "Default Category", "id": 2, "url_path": null, "breadcrumbs": null }, { "name": "Women", "id": 20, "url_path": "women", "breadcrumbs": null }, { "name": "Tops", "id": 21, "url_path": "women/tops-women", "breadcrumbs": [ { "category_id": 20, "category_name": "Women", "category_level": 2 } ] }, { "name": "Toddlers", "id": 51, "url_path": "toddlers", "breadcrumbs": null } ] } ] } } }
Please provide Severity assessment for the Issue as Reporter. This information will help during Confirmation and Issue triage processes.
- Severity: S0 - Affects critical data or functionality and leaves users without workaround.
- Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
- Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
- Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
- Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.
sirugh
Metadata
Metadata
Assignees
Labels
Area: APIsComponent: GraphQLGraphQLGraphQLIssue: ConfirmedGate 3 Passed. Manual verification of the issue completed. Issue is confirmedGate 3 Passed. Manual verification of the issue completed. Issue is confirmedPAPPartners acceleration programPartners acceleration programPriority: P1Once P0 defects have been fixed, a defect having this priority is the next candidate for fixing.Once P0 defects have been fixed, a defect having this priority is the next candidate for fixing.Progress: doneProject: GraphQLReproduced on 2.4.xThe issue has been reproduced on latest 2.4-develop branchThe issue has been reproduced on latest 2.4-develop branch
Type
Projects
Status
Done