Evaluation Form: Challenge Assignment

[r-bartlett-gsa]

User Story

As a challenge manager, in order to have appropriate evaluation forms linked to my challenges, I would like to assign a challenge and challenge phase to an evaluation form.

Acceptance criteria:

• [ ] A challenge manager can select a single challenge / challenge phase from a list of challenges they have available on their account within an evaluation from creation workflow
  • [ ] If the selected challenge has phases, they are listed as separate challenge entries in the list
• [ ] Already assigned challenges or challenge phases to other evaluation forms do not display in the list
• [ ] An assigned challenge and a challenge phase ties the evaluation form to all submissions of that challenge / phase
  • [ ] When an evaluator opens a submission to evaluate, a correct evaluation from is displayed, #90

Development tasks:

• [ ] Task 1
• [ ] Task 2

Definition of Done

Doing (dev team)

• [ ] Code complete
• [ ] Code is organized appropriately
• [ ] Any known trade offs are documented in the associated GH issue
• [ ] Code is documented, modules, shared functions, etc.
• [ ] Automated testing has been added or updated in response to changes in this PR
• [ ] The feature is smoke tested to confirm it meets requirements
• [ ] Database changes have been peer reviewed for index changes and performance bottlenecks
• [ ] PR that changes or adds UI
  • [ ] include a screenshot of the WAVE report for the altered pages
  • [ ] Confirm changes were validated for mobile responsiveness
• [ ] PR approved / Peer reviewed

• [ ] Move card to testing column in the board

  Testing (dev team)

• [ ] Security scans passed
• [ ] Automate accessibility tests passed
• [ ] Build process and deployment is automated and repeatable
• [ ] Feature toggles if appropriate
• [ ] Deploy to staging

Staging

• [ ] Accessibility tested (Marni)
  • [ ] Keyboard navigation
  • [ ] Focus confirmed
  • [ ] Color contrast compliance
  • [ ] Screen reader testing
• [ ] Usability testing: mobile and desktop (Tracy or Marni)
• [ ] Cross browser testing (tool to be determined) (Tracy or Marni)
  • [ ] UI rendering is performant
• [ ] AC review (Renata)
• [ ] Deploy to production (production-like environment for eval capability) (dev team)

• [ ] Move to production column in the board

  Production

• [ ] User and security documentation has been reviewed for necessary updates (Renata/Tracy/Dev team)
• [ ] PO / PM approved (Jarah or Renata)
• [ ] AC is met and it works as expected (Jarah or Renata)
• [ ] Move to done column in the board (Jarah or Renata)

[r-bartlett-gsa]