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

Update Continuation In NR flow #16637

Closed
6 of 8 tasks
severinbeauvais opened this issue Jun 2, 2023 · 4 comments
Closed
6 of 8 tasks

Update Continuation In NR flow #16637

severinbeauvais opened this issue Jun 2, 2023 · 4 comments
Assignees
Labels
ENTITY Business Team SRE SRE team task UX Assurance

Comments

@severinbeauvais
Copy link
Collaborator

severinbeauvais commented Jun 2, 2023

Diagram: https://preview.uxpin.com/a86dccdd20ac62828f965c5eea10f81b828a9853#/pages/163147814/simulate/sitemap
Wireframes: https://preview.uxpin.com/a86dccdd20ac62828f965c5eea10f81b828a9853#/pages/163147816/simulate/sitemap

(This is the same as existing Relocate Into flow.)

  • Hide jurisdiction. already done in 17152
  • For Coop don't show numbered.
  • Leave Societies code alone.
  • Re-use the existing feature flag for link to COLIN (until BC/CCC/ULC are released).
  • Verify remaining flow.
  • Create unit tests.
  • Use FF to determine whether to redirect to COLIN or Continue In Now
  • For numbered continuation in, the action button should be "Continue In Now"
    • create draft filing (FUTURE TICKET)
    • redirect to business dashboard (FUTURE TICKET)
    • optional what you implement for this part since we haven't yet implement Continuation In filings/drafts
@ketaki-deodhar
Copy link
Collaborator

ketaki-deodhar commented Aug 4, 2023

Test Notes:

Here is the temp URL: https://namerequest-dev--pr-639-c9rqzr4l.web.app/

  • Continuation In flow works as expected but there are some UX changes which were not implemented in this ticket. Implementation is based on previous designs/wireframes. Please see ticket# 17297
  • For Approved NR, "Continue In Now" button is not displayed as these type of applications are not in place yet
  • "Colin" link is not shown either because staff does not go to Colin for this flow; they go to Name Examination. This is based on discussion with the team (refinement/scrum meeting this morning)

@yuisotozaki
Copy link

Ready for QA with the notes above in mind.

@severinbeauvais severinbeauvais changed the title Update Continuation In flow Update Continuation In NR flow Aug 9, 2023
@Mihai-QuickSilverDev
Copy link
Collaborator

Mihai-QuickSilverDev commented Aug 11, 2023

@severinbeauvais Can this ticket be closed on our board?

@severinbeauvais
Copy link
Collaborator Author

This is in a Namerequest UI feature branch that SRE will deploy for us in the future.

I don't remember what @jdyck-fw does for these kinds of tickets. They need to be tracked for deployment/QA somehow...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ENTITY Business Team SRE SRE team task UX Assurance
Projects
None yet
Development

No branches or pull requests

5 participants