Evaluation Recusal

[r-bartlett-gsa]

User story

As an evaluator, in order to provide fair evaluation for the submission the public solvers submitted, I would like to be able to indicate if I am not able to evaluate the submission I am assigned to.

Acceptance criteria:

• On a submission detail view for an evaluator, there's an option to recuse from evaluating a submission:
  • A warning message is displayed asking evaluator to confirm recusal
• The recusal is saved as a submission evaluation status and is displayed throughout workflows for the evaluator and for the challenge manager
  • Recusal alert is displayed for the challenge manager, Recused Evaluator Alert #77
• The submission remains assigned to the evaluator until a challenge manager unassigns the evaluator from the submission, Unassign Evaluators from a Submission #76
  • If an evaluator has any scores saved on the submission, the scores are removed along with removing evaluator assignment

Dev tasks:

• Evaluators can update recused assignment status #297

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.