-
Notifications
You must be signed in to change notification settings - Fork 21
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
Regression: Restore cancel_at being set for new subscriptions #1437
Comments
…ns which have cancel_at date set
…ns which have cancel_at date set
🚀 Issue was released in |
6 similar comments
🚀 Issue was released in |
🚀 Issue was released in |
🚀 Issue was released in |
🚀 Issue was released in |
🚀 Issue was released in |
🚀 Issue was released in |
🚀 Issue was released in |
11 similar comments
🚀 Issue was released in |
🚀 Issue was released in |
🚀 Issue was released in |
🚀 Issue was released in |
🚀 Issue was released in |
🚀 Issue was released in |
🚀 Issue was released in |
🚀 Issue was released in |
🚀 Issue was released in |
🚀 Issue was released in |
🚀 Issue was released in |
🚀 Issue was released in |
13 similar comments
🚀 Issue was released in |
🚀 Issue was released in |
🚀 Issue was released in |
🚀 Issue was released in |
🚀 Issue was released in |
🚀 Issue was released in |
🚀 Issue was released in |
🚀 Issue was released in |
🚀 Issue was released in |
🚀 Issue was released in |
🚀 Issue was released in |
🚀 Issue was released in |
🚀 Issue was released in |
Is your feature request related to a problem? Please describe.
A refactor in update_subscription statuses, caused cancel_at not being set on new plans if this setting was chosen (and missing test which exists ,
@516_subscriber_order_plan_with_cancel_at
but was missing from automated test runs).Describe the solution you'd like
cancel_at
and include test in test run.Describe alternatives you've considered
Additional context
TODO add consistency to test run naming so that inclusion of all existing tests may be valitated automatically (missing no tests).
The text was updated successfully, but these errors were encountered: