Submissions List View for Challenge Managers

[r-bartlett-gsa]

User story

As a challenge manager, in order to manage submissions and their evaluations process efficiently, I would like to be able to access all submissions for a single challenge.

Acceptance Criteria:

• A challenge manager can view a list of submission for each challenge they manage
  • The submission list view indicates the challenge
  • An evaluation progress summary is displayed, Evaluation Progress Summary/Dashboard for Challenge Managers #79
  • A challenge manager can export submission data, Export Submissions #58
  • The list of submissions displays the following information for each submission:
    • Submission ID
    • Eligibility for evaluation status
    • Advancement status
    • Assigned evaluators and their evaluation status (not started, in progress, completed, recused)
    • Average score (only available when all assigned evaluators completed their evaluations)
    • An option to view submission, Submission Detail View for Challenge Managers #80
  • A challenge manager can sort the list, Sort & Filter Submissions #57
    • Default sort is: no assigned evaluators, not started, in progress, completed, not eligible for evaluations
  • Alerts are displayed to inform challenge managers whether they need to reassign evaluators or update their evaluation forms:
    • If a challenge does not have assigned evaluation form
    • If a submission has a recused evaluator
• The page displays 20 submissions on initial load, and the user can load more submission in 20 submission increments

Development tasks:

• Create evaluator_submission_assignments table #205
• Create View Submissions page #206
• Add warning messages "No Evaluation Form" "Recused Evaluator" #208
• Create Total Submissions stats component #209
• Add evaluation status details to the list #291
• Update submission Eligible for Evaluation / Selected to Advance from list view #292
• Submissions list view data is limited and loads more data on demand #293

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.

[r-bartlett-gsa]

@stepchud This is the user story that includes the "load more" option for the submissions list view.

The average number of submissions for a challenge (on challenge.gov) is 46.3 submissions. The max number of submissions for a single challenge is 517.

So loading in 20 submissions increment seems reasonable. Do you think there will be performance issues when a challenge has 500-1000 submissions?

[stepchud]

@r-bartlett-gsa everything on this specific list view can be QA'd except Exports, which shouldn't impact anything else on here functionally.
wrt your question about performance, it's hard to predict performance without realistic testing, but I'd guess this can handle up to 1000 submissions on the table. I would treat high-volume performance as a future concern.