- Notifications
You must be signed in to change notification settings - Fork 9.4k
Closed
Closed
Copy link
Labels
Area: APIsComponent: CustomerGraphQlIssue: ConfirmedGate 3 Passed. Manual verification of the issue completed. Issue is confirmedGate 3 Passed. Manual verification of the issue completed. Issue is confirmedPriority: 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: GraphQLReported on 2.4.2Indicates original Magento version for the Issue report.Indicates original Magento version for the Issue report.Reproduced on 2.4.xThe issue has been reproduced on latest 2.4-develop branchThe issue has been reproduced on latest 2.4-develop branchSeverity: S1Affects critical data or functionality and forces users to employ a workaround.Affects critical data or functionality and forces users to employ a workaround.
Description
Customer type is_subscribed field value is taken from the customer website: https://github.com/magento/magento2/blob/2.4-develop/app/code/Magento/CustomerGraphQl/Model/Resolver/IsSubscribed.php#L52
When you're updating the subscription via createCustomer/createCustomerV2/updateCustomer/updateCustomerV2 mutation the subscription store is taken from the current store: https://github.com/magento/magento2/blob/2.4-develop/app/code/Magento/CustomerGraphQl/Model/Customer/UpdateCustomerAccount.php#L115
Preconditions (*)
- Magento version 2.4.2(probably more)
- At least 2 websites
- Customer Global accounts enabled
Steps to reproduce (*)
- Create customer account in the 1st website
- Subscribe to newsletter from the 2nd website
- Confirm your subscription
Expected result (*)
- Customer can see that he's subscribed
Actual result (*)
- Customer can't see that he's subscribed as the subscription data is taken from the website he created his account in, but the subscription is created for the website/store he was browsing from when updating the subscription.
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”.
Metadata
Metadata
Assignees
Labels
Area: APIsComponent: CustomerGraphQlIssue: ConfirmedGate 3 Passed. Manual verification of the issue completed. Issue is confirmedGate 3 Passed. Manual verification of the issue completed. Issue is confirmedPriority: 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: GraphQLReported on 2.4.2Indicates original Magento version for the Issue report.Indicates original Magento version for the Issue report.Reproduced on 2.4.xThe issue has been reproduced on latest 2.4-develop branchThe issue has been reproduced on latest 2.4-develop branchSeverity: S1Affects critical data or functionality and forces users to employ a workaround.Affects critical data or functionality and forces users to employ a workaround.
Type
Projects
Status
Done