526ez | Reorder pages

[Mottie]

Description

Move a few pages within Form 526 around to organize the flow a bit more.

• Flow diagram: https://app.mural.co/t/vsa8243/m/vsa8243/1639070794497/b605ba85a76c75be7d195bd4090286b6e8061453?sender=kstachura1551

Tasks

• [ ] Reorder 526 page to match design
• [ ] Ensure page dependencies don't break, i.e. one page must come before another

Definition of Ready

• [ ] Clear value discription
• [ ] Testable acceptance criteria
• [ ] Accessibility added to acceptance criteria
• [ ] Approved designs attached
• [ ] Sample data provided where appropriate
• [ ] Estimated to fit within the sprint
• [ ] Dependencies and blockers linked

---

How to configure this issue

• [ ] Attached to a Milestone (when will this be completed?)
• [ ] Attached to an Epic (what body of work is this a part of?)
• [ ] Labeled with Team (product support, analytics-insights, operations, service-design, Console-Services, tools-fe)
• [ ] Labeled with Practice Area (backend, frontend, devops, design, research, product, ia, qa, analytics, contact center, research, accessibility, content)
• [ ] Labeled with Type (bug, request, discovery, documentation, etc.)

[Mottie]

This work was not done this sprint. We need to discuss the flow changes and if they need to be behind a feature flag. Putting the changes behind a feature will significantly increase the amount of code required to finish this work.

[saderagsdale]

• Previous team thought we could optimize the form, but this is just a hypothesis.
• Needs research and design focus.
• Place on hold and attached to any related investigations.