Edit Evaluator's Score

[r-bartlett-gsa]

User story

As a challenge manager, in order to ensure that the final submission score encompasses all considerations and deliberations of the evaluation processes, I would like to be able edit the scores submitted by the evaluators

Acceptance criteria:

• [ ] A challenge manager can edit the score submitted by each evaluator for each submission
  • [ ] A challenge manager can overwrite evaluator's entered scores or criteria option selections
  • [ ] A challenge manager can NOT edit evaluator's feedback
  • [ ] A challenge manager can provide a justification note for each criteria and for the entire form
  • [ ] Both evaluator's and revised scores are displayed for the challenge manager for each criteria and as a total
  • [ ] A challenge manager is asked to confirm the edited score (is displayed a warning message)
  • [ ] Revised scores and justification notes are saved within the submission details page for the challenge manager and the evaluator
• [ ] After the score is edited and saved by the challenge manager, the revised score is used for final score average calculation
  • [ ] If the score is revised, it is indicated so in the submission list views

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.