Backlog

MVP for Proof of Concept

• Run through main flow in single session:
  • Create order
  • Print QR code and attach to a flag box with printout
  • Manual test: "Scan" QR code, or "scan" button, through all phases, logging in as different users
• Take off ominous component "Remove All" from order list. (PR 68)
• Create users for US state congressional offices (e.g. MD-01) to match already created admins for them (e.g. MD-01-ADMIN)

MVP for Release

• Change password by user (Terence)
• Admin: Change password of user (Rajinder)
• Force change pw on first log in unless env var CHANGE_ON_FIRST_LOGIN in backend is N (Terence)
  • That is, when congressional user signs in for the first time, prompt them to set a password.
• Admin: Documentation on changing admin password from backend in case it is lost (Ethan)

Other

• Write up security/UI rules for updating status and adding office code (Ethan) (find link from Ethan on slack)

• Restrict state office users to only see orders associated with their office

• Implement rules

• UI: Security (Aaron)

  • Display user name on the screen
  • Route to login page if not logged in

• UI (to discuss):

  • Condensed output that displays 20+ orders on the screen at one time

• UI/Backend: User maintenance (Ethan?)

  • list user endpoint
  • update user endpoint
  • users menu option to replace add users (only -ADMIN can access this page)
    • click to get List of Users (see all users for their office)
      • click on user -> Edit User Info
        • Edit User screen -> change password or edit any field, delete

• Generic Error handling

• Error handling: duplicate order

• Backend: File structure (Terence/Ethan)

• Backend: Log table (Terence)

• Backend: Security on the backend for updating status for STATE office staff

• Backend: toBeFlown key:value pair to be added to Order Model

  • Frontend: ability to set toBeFlown at Order creation (add order)
  • Frontend: ability to edit toBeFlown from Edit Order view
  • Frontend: update Skip functionality to use toBeFlown to skip AOC all together instead of just AOC_FLOWN status (Merritt)

• Development Guide:

  • Configuring Local App to Use Heroku (section temporarily removed because it contained Heroku pwd information, section to be rewritten to hide sensitive information?) (Ethan)

• More tests

• update React Router (optional)

ON HOLD - MVP for Implementation

• Identify how orders are entered
• Hosting plan
• Support plan
• Data backup/recovery plan
• Training / rollout plan
• Review and approval from Flag committee of above

Dry Run Mar 11 Demo Plan:

• Open site on computer with screen share

• "Scan" QR Code

• Advance the status

• sort by order status descending.

• Search for a flag

• Press edit button and show how you can change a flag

• Walk through of flow

• Run Cypress testing npm run cypress:open (or 'npm run cypress'??)

• Important Mentions

  • Flag audit trail / order log (to mention)
  • Congressional users can only see flags for their office
  • In future version, will give choice of viewing "active" orders where you need to take action or "all"
  • Security Document
  • Ask about status skips for to_be_flown boolean