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

Enrollment errors should redirect user to the Payment Error page / retry view #1903

Closed
1 task
thekaveman opened this issue Feb 22, 2024 · 1 comment
Closed
1 task
Labels
back-end Django views, sessions, middleware, models, migrations etc. front-end HTML/CSS/JavaScript and Django templates

Comments

@thekaveman
Copy link
Member

thekaveman commented Feb 22, 2024

This is a follow-up to the design work from #1137 and a prerequisite to the new designs coming with #1865. This is related to the refactoring happening in #1848.

We already have the enrollment:retry view implemented with the associated design for the Payment Error page in Figma.

This task is to ensure that any error raised during the enrollment process sends the user to this retry view instead of the generic application error view.

Acceptance Criteria

  • Errors raised during enrollment are handled by the retry view/page instead of the generic app "Service Down" error page
@thekaveman thekaveman added front-end HTML/CSS/JavaScript and Django templates back-end Django views, sessions, middleware, models, migrations etc. labels Feb 22, 2024
@thekaveman thekaveman added this to the Back Office API Enrollment milestone Feb 22, 2024
@thekaveman thekaveman self-assigned this Feb 27, 2024
@thekaveman thekaveman moved this from Todo to In Progress in Digital Services Feb 27, 2024
@thekaveman thekaveman linked a pull request Mar 11, 2024 that will close this issue
@thekaveman thekaveman moved this from In Progress to Todo in Digital Services Mar 11, 2024
@thekaveman thekaveman removed their assignment Mar 11, 2024
@thekaveman thekaveman removed this from the Back Office API Enrollment milestone Mar 13, 2024
@thekaveman
Copy link
Member Author

We're doing a separate handoff for the new error screens, with tickets that will supersede this one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
back-end Django views, sessions, middleware, models, migrations etc. front-end HTML/CSS/JavaScript and Django templates
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

1 participant