Submission Award / Advancement

[r-bartlett-gsa]

User story

As a challenge manager, in order to keep track which submission are deemed as winners, I would like to be able to indicate winning submissions.

Notes:

• This is a current functionality on Phoenix app, with submission migration to the Rails, ability to mark awardees/advancement and associated rules need to also be available on the Rails.
  • If a challenge is multi-phased and the second phase is limited only to the previous phase awardees, then only solvers with submissions selected for advancement can participate in later phase entries

Acceptance criteria:

• [ ] On a submission details view for a challenge manager, if all assigned evaluators completed their evaluations, a challenge manager can indicate if a submission is selected to advance
• [ ] Once a submission is marked as selected to advance, the evaluation process for that submission is considered completed and a challenge manager can no longer assign any new evaluators or change any scores of existing evaluators
• [ ] Advancement status is visible on the submission list view, #82
• [ ] Submissions can be sorted by the advancement status, #57
• [ ] Advancement indication can be reversed as many times as needed, enabling a challenge manager to assign evaluators and change scores again

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.