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.

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

User Status in Evaluator List for Existing Users #287

Open
16 of 38 tasks
r-bartlett-gsa opened this issue Nov 22, 2024 · 0 comments · May be fixed by #341
Open
16 of 38 tasks

User Status in Evaluator List for Existing Users #287

r-bartlett-gsa opened this issue Nov 22, 2024 · 0 comments · May be fixed by #341
Assignees

Comments

@r-bartlett-gsa
Copy link
Member

r-bartlett-gsa commented Nov 22, 2024

As a challenge manager, in order to have a better understanding of evaluator's availability, I would like an additional user status that is associated with existing users that need their role changed.

Acceptance criteria:

  • When an evaluator is added to the evaluator list (evaluation panel), and they are already in challenge.gov system under a different role, their user status indicates "Role Change Needed"
  • When their role is changed to an evaluator by the admin, their user status becomes "Available"

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

  • Usability testing: mobile and desktop (Tracy or Marni)
  • Accessibility tested (Marni)
    • Keyboard navigation
    • Focus confirmed
    • Color contrast compliance
    • Screen reader testing
  • 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)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants