You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
BUG no 1 observe that the subscription overview page does not show that there are scheduled changes to the subscription
Go back to the subscription management flow
Select "Cancel Subscription"
BUG no 2 Note that it's not possible to finish the flow
Expected Result
Cancelling the subscription the first time should update the UI to indicate that there are scheduled changes.
Cancelling the subscription should not show a "cancel subscription" button on the subscription management flow (because it's already cancelled)
Actual Result
Without hard refreshing the app it's not possible to see that changes to the subscription have been scheduled once the cancellation flow is complete
Once the scheduled changes are available in the UI it's still possible to attempt to cancel your subscription again but the process actually broken and can't be completed (giving the impression that we're preventing users from cancelling)
Environment
SaaS (https://sentry.io/)
Steps to Reproduce
Expected Result
Cancelling the subscription the first time should update the UI to indicate that there are scheduled changes.
Cancelling the subscription should not show a "cancel subscription" button on the subscription management flow (because it's already cancelled)
Actual Result
Without hard refreshing the app it's not possible to see that changes to the subscription have been scheduled once the cancellation flow is complete
Once the scheduled changes are available in the UI it's still possible to attempt to cancel your subscription again but the process actually broken and can't be completed (giving the impression that we're preventing users from cancelling)
Product Area
Settings - Subscription
Link
https://sentry.zendesk.com/agent/tickets/140353
DSN
No response
Version
No response
The text was updated successfully, but these errors were encountered: