Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Dashboard Updates - Evaluator (Rails) #376

Open
49 tasks
r-bartlett-gsa opened this issue Jan 28, 2025 · 3 comments · May be fixed by #435
Open
49 tasks

Dashboard Updates - Evaluator (Rails) #376

r-bartlett-gsa opened this issue Jan 28, 2025 · 3 comments · May be fixed by #435
Assignees
@stonefilipczak
Milestone
Sprint 03/11/25

Comments

@r-bartlett-gsa
Copy link
Member

r-bartlett-gsa commented Jan 28, 2025 •
edited
Loading

User Story

As an evaluator, in order to easily and quickly find various tasks associated with evaluating a submission, I would like to see a list of challenges with submissions assigned to me.

Acceptance Criteria:

  • Current Dashboard page with blue cards is eliminated and instead Evaluations (/evaluations) becomes the main evaluations dashboard page that the evaluator sees after logging in
  • The page consist of the following components:
    • Challenges list
      • If an evaluator does not have any submissions assigned to them yet, a warning message is displayed indicating so
      • If an evaluator has submissions assigned, a table is displayed:
        • # of submissions to evaluate - links to the Submissions list page on the Rails app
          • The number indicates total assigned submissions and remaining submissions to evaluation (e.g. 4 of 5 submissions)
        • Evaluation due date
        • Evaluation status
      • The table displays all challenges/phases for which the evaluator has submissions to evaluate
    • Resources section
  • Designs 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)
@r-bartlett-gsa
Copy link
Member Author

r-bartlett-gsa commented Jan 28, 2025 •
edited
Loading

Image

@r-bartlett-gsa r-bartlett-gsa mentioned this issue Nov 8, 2024
Open
44 tasks
@r-bartlett-gsa r-bartlett-gsa added this to the Sprint 02/25/25 milestone Feb 12, 2025
@stepchud
Copy link
Contributor

stepchud commented Feb 14, 2025 •
edited
Loading

@r-bartlett-gsa Is this requirement necessary?

  • The table displays 10 challenges by default; if there are more than 10 challenges Show More button is available and loads more challenge in increments of 10

I think the likelihood of this is extremely small and instead of paginating, it should just filter out the challenge phases that are finished/closed in case they have a long history of evaluating challenges (but even that is more of an optimization for later, not MMP scope)

@r-bartlett-gsa
Copy link
Member Author

@r-bartlett-gsa Is this requirement necessary?

  • The table displays 10 challenges by default; if there are more than 10 challenges Show More button is available and loads more challenge in increments of 10

I think the likelihood of this is extremely small and instead of paginating, it should just filter out the challenge phases that are finished/closed in case they have a long history of evaluating challenges (but even that is more of an optimization for later, not MMP scope)

I agree, I removed it from AC, and will update Figma.

@r-bartlett-gsa r-bartlett-gsa linked a pull request Feb 20, 2025 that will close this issue
[376] Evaluator Dashboard #435
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@stonefilipczak stonefilipczak

Labels
None yet
Projects
None yet
Milestone
Sprint 03/11/25
Development

Successfully merging a pull request may close this issue.

[376] Evaluator Dashboard GSA/Challenge_platform
3 participants
@stepchud @stonefilipczak @r-bartlett-gsa