A&R -> Improve variance navigation

[meyerdarcie]

Description:

In A&R admin, once you review a piece data from the review tab, it takes you out of the tab and the only way back is to use the browser’s back button, otherwise you need to reselect "Review Data" and then re-search your variances.

This ticket is to consider adding another button (e.g., "Return to Review Data Search") to improve the navigation.

Example of variance search result. Clicking on View/Edit opens the data entry screen:

once you click "View/Edit", you have the option of clicking “Cancel” or “Save” edits:

Selecting either “Cancel” or “Save” takes you the data entry screen for that park/ month. You have to re-navigate to “Review Data” to continue reviewing variances.

Acceptance Criteria:

[Note: Use 'Given/When/Then' format if it makes sense to. Otherwise, a simple checklist that can be tested.]

Development Checklist:

• [ ] ...
• [ ] ...
• [ ] ...

Dependencies

• Blocked by
• Blocking

Relevant documentation as reference

Definition of Ready

• [ ] Acceptance criteria are included
• [ ] Wireframes are included (if applicable)
• [ ] Design / Solution is accepted by Product Owner (if applicable)
• [ ] Dependencies are identified (technical, business, regulatory/policy)
• [ ] Story has been estimated (under 13 pts)

Definition of Done

• In progress:
  • [ ] Acceptance criteria are tested (Functionality meets the acceptance criteria defined in the ticket)
  • [ ] UI meets accessibility requirements
  • [ ] Unit tests are written
  • [ ] Work is traceable in GitHub
  • [ ] PR linked to ticket number
  • [ ] If needed/required - Dev adds flag/label to highlight any migration steps necessary prior to PROD deployment
• Code review:
  • [ ] Code is peer reviewed and has passed CI/CD tests
• QA:
  • [ ] Acceptance criteria are tested (Functionality meets the acceptance criteria defined in the ticket)
  • [ ] Code is potentially shippable to the production environment
  • [ ] Functional features have been tested and passed by QA
  • [ ] UI components tested by designer
  • [ ] Code is deployed to PROD when moved to 'done' column (unless requested otherwise by PO)
• PO Review:
  • [ ] Acceptance criteria are tested (Functionality meets the acceptance criteria defined in the ticket)
  • [ ] Reviewed and approved by Product Owner

Notes:

[LindsayMacfarlane]

Backlog refinement (October 8): This ticket to be implemented for spring season.