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

Implement situational enablement of split UPE feature flag to facilitate rollout #5503

Closed
FangedParakeet opened this issue Feb 1, 2023 · 1 comment
Assignees
Labels
component: upe priority: critical The issue is critical—e.g. a fatal error, security problem affecting many customers.

Comments

@FangedParakeet
Copy link
Contributor

Description

Please read this thread for more details on this issue.

We are planning to roll out the split UPE project gradually behind a feature flag that is under development in #5353 (WIP PR in #5496). We would like to implement some custom rules, so that users who are new to the UPE or WCPay have this feature enabled automatically, whereas existing customers using the current UPE implementation are not automatically and unwillingly migrated to the split UPE feature.

Acceptance criteria

We seek to implement the following rules.

  • New stores that register with WCPay automatically have the split UPE flag enabled.
  • Existing stores that are already registered with WCPay, but do not currently have any version of the UPE enabled via the current feature flag, will enable the split UPE flag when they decide to enable the "new checkout experience" in their WCPay settings.
  • Existing stores that do have some version of the UPE enabled via the current feature flag will not automatically find that the new split UPE flag is enabled.
  • Existing stores that do have some version of the UPE enabled via the current feature flag can enable the split UPE feature flag by disabling the "new checkout experience" and then re-enabling it.

Additional context

p1674500132021179/1674491221.244469-slack-C048UEB37MZ
#5353
#5496

@FangedParakeet FangedParakeet added status: blocked The issue is blocked from progressing, waiting for another piece of work to be done. component: upe labels Feb 1, 2023
@FangedParakeet
Copy link
Contributor Author

Hey team! Please add your planning poker estimate with Zenhub @mdmoore @timur27

@frosso frosso added the priority: critical The issue is critical—e.g. a fatal error, security problem affecting many customers. label Feb 4, 2023
@mdmoore mdmoore assigned mdmoore and unassigned mdmoore Feb 4, 2023
@frosso frosso removed the status: blocked The issue is blocked from progressing, waiting for another piece of work to be done. label Feb 9, 2023
@frosso frosso closed this as completed Feb 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component: upe priority: critical The issue is critical—e.g. a fatal error, security problem affecting many customers.
Projects
None yet
Development

No branches or pull requests

4 participants