User story

As an evaluator, in order to evaluate a submission, I would like to be able to enter and submit the scores for the submission I'm evaluating.

Acceptance Criteria:

• Within an evaluation form view for an evaluator, an evaluator can enter information or select choices for each criteria in the evaluation form
  • Evaluation form entries are validated against score/weight values as setup by the challenge manager
• Changes to evaluation criteria scores and total score are updated as the evaluator changes the form
  • Score values are displayed for each criteria and in total at the bottom of the form
  • An evaluator can enter comments for each criteria and for the entire evaluation form
• An evaluator can save the form as a draft, saving all entries
  • Draft form scores are calculated but are not displayed for challenge manager in any views
  • An evaluator only sees draft scores within the evaluation form view
  • Draft scores are not used for average score calculation
  • If an evaluator saved the form as a draft, the submission evaluation progress is considered "in progress" across all views (and can be filtered by)
    • An evaluation form that has no entries and is not saved as a draft is considered as "not started" status across all views (and can be filtered by)
• An evaluator can complete and submit the scores, if the entries are provided for all required fields
  • If not all entries are provided for the required fields, an evaluator cannot complete and submit the form
  • When the evaluation form is completed and submitted, a confirmation is displayed for the evaluator
  • Completed and submitted scores are used for calculation of the final score and an average score, and are displayed in other views for the challenge manager and evaluator
  • Completed form cannot be edited by the evaluator
  • If the form is completed, the form status is considered completed, and the status is displayed (and can be filtered by) across other views

Development tasks:

• Evaluations routes & controller #298
• Submission scoring - view-only evaluation form #299
• Submission scoring - save as draft #300
• Submission scoring - complete and submit scores #301
• Evaluation Recusal #91

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)