Submission Eligibility for Evaluation (Prescreening)

[r-bartlett-gsa]

User story

As a challenge manager, in order to ensure that only the submission that satisfy all the competition requirements proceed to an evaluation process, I would like to be able to indicate that the submission is eligible for evaluation.

Acceptance criteria:

• [ ] On a submission details view for a challenge manager, a challenge manager can indicate whether the submission is meeting competition requirements and is eligible for evaluation
• [ ] Only eligible for evaluation submissions can move to the evaluation steps (evaluator assignment, evaluation process, advancement)
• [ ] A challenge manager cannot assign evaluators or advance submission to the next phase if it is not marked as eligible for evaluation
• [ ] Evaluation eligibility status is visible on the submission list view, #82
• [ ] Submissions can be sorted by the eligibility status, #57

Dev 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
• [ ] Security scans passed
• [ ] Automate accessibility tests passed
• [ ] Build process and deployment is automated and repeatable
• [ ] Feature toggles if appropriate
• [ ] Deploy to staging

• [ ] Move card to testing column in the board

  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 - UI rendering is performant on below listed devices/browsers (Tracy or Marni)
  • [ ] Windows/Chrome
  • [ ] Windows/Edge
  • [ ] Mac/Chrome
  • [ ] Mac/Safari
  • [ ] iOS/Safari
• [ ] 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]

Some button styles, colors and labels may have changed and screenshots below may reflect outdated styles. Please refer to Figma for latest designs. Misalignment in styles, colors and labels should not affect the completion of development work. There will be additional user stories towards the end of this epic or MVP to bring uniformity to styles and colors. If significant difference is noticed in features / functionality, please contact Renata.