Assign Evaluators to a Submission - Manual

[r-bartlett-gsa]

User story

As a challenge manager, in order to have the submission of my challenge reviewed and scored by evaluators, I would like to be able to assign evaluators to submissions.

Acceptance criteria:

• [ ] Under each submission detail view, a challenge manager can assign as many evaluators as needed from the the available evaluators list
• [ ] Evaluators can only be assigned if the submissions is checked as eligible for evaluations / is prescreened
• [ ] Only users that meet the following criteria can be assigned to the submission of the challenge:
  • [ ] User with evaluator role and approved accounts
  • [ ] Evaluators that are part of the evaluator list for that challenge
  • [ ] Evaluators that are not recused
  • [ ] Evaluators that are not unassigned
• [ ] A challenge manager has an option to review their challenge evaluator list by clicking on the link button at the bottom of the available evaluators list
• [ ] Evaluators evaluation progress is tracked for that submission
• [ ] When an evaluator is assigned to a submission, that submission appears on the evaluator's list of submissions #88
• [ ] When an evaluator is assigned to a submission, that evaluator appears on the challenge manager's list of submissions #59

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.

Mobile

Desktop