Submission Detail Page Updates - Challenge Manager

[r-bartlett-gsa]

User Story

As a challenge manager, in order to accomplish all tasks associated with my challenge management in a consistent way, I would like submission and evaluation workflows to be consistent in design and styles with other eval site features.

Acceptance Criteria:

• When a challenge manager clicks on a submission ID link on the submission list page, they are sent to the submission detail view that consist of the submission information and evaluation process management functions (eligibility for evaluation, selection for advancement, notes, available and assigned evaluator tables)
• Page H1 is Challenge Title (if it's a phased challenge, the phase is indicated in the H1)
• Page H2 is "Submissions [ID]"
• A challenge manager can minimize submission information section, or open it in a new tab
  • On desktop the arrow button to minimize the submission information sticks on the screen as the challenge manager scrolls the page
• Eligible for Evaluation and Selected to Advance checkboxes are functional independently (do not require a save button to save selection)
• Save Notes button saves the Notes field input only
• Available and Assigned Evaluator tables are wrapped in accordions
  • Available evaluator table displays only the users with an evaluator role that are added to the evaluation panel for this challenge and have available user status
  • The table consists of the following headers:
    • Name - links to the Evaluator's submission list page
    • Email address update: col was removed
    • # of assigned submissions
    • Action - Assign or reassign buttons
    • An informational alert is displayed with link to the evaluation panel
  • Assigned Evaluators table consists of the following headers:
    • Name - links to the Evaluator's submission list
    • Evaluation status
    • Score - If evaluation completed, "View Evaluation" link is displayed next to the score and takes the challenge manager to the Evaluation form view
    • Action - Unassign button
• Designs (colors, fonts, labels, etc) match wireframes in Figma: https://www.figma.com/design/sLkJM1Ua9Zu3HW2h4mVdgr/Challenge.gov-Eval-(Updated-01%2F27%2F25)?node-id=7003-153455&t=G2WnCXJa1OXhZSU3-1

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 (Renata)
• AC is met and it works as expected (Renata)
• Move to done column in the board (Renata)