User Story

As a developer
I'd like to have Vuex implemented
So that I can store user tokens and other data in state management

Acceptance Criteria

• Vuex and /store properly setup
• user tokens are saved to state when logged in
• PR merged to master

Task

What is their current point of contact, how do they keep that information current with the city, what types of contacts do they have access to, what are their pain points, barriers, etc.

Acceptance Criteria

• New documentation created from findings
• PR merged to master with above changes

Task

Research why this system will exist. Is it to fulfill a legal requirement, facilitate response, etc?

Acceptance Criteria

• TechSpec updated with research or new documentation created from findings
• PR merged to master with above changes

User Story

As an end user
I'd like to have the ability to add titles and other attributes to contacts
So that I can add extra context to a contact

Acceptance Criteria

• Contact form has new fields to add desired functionality
• Contact form allows user to add custom attributes and information to the contact form
• Custom attributes are properly stored and displayed
• PR merged to master

Notes

Dependant on this issue CodeForBaltimore/Bmore-Responsive#91 - Add attribute columns to all types

Task

As a developer or partner of the project, I want to see what technologies are being deployed.

Notes

User Story

As a developer
I'd like to interact with the backend application using an API
So that I can build an efficient front end and user experience.

Acceptance Criteria

• API spec added to documents
• API available in the backend
• PR merged to master with API code.

User Story

As a developer
I'd like to setup VueJS for the front-end
So that I can develop a Vue application

Acceptance Criteria

• VueJS is powering the front-end
• PR merged to master with above change

Notes

Dependant on #18

User Story

As a developer or end use
I'd like to have detailed and accurate tech specs and documentation
So that I can understand this project and its goals

Acceptance Criteria

• Items in /docs are up to date and reflect the project in its current state
• Same as ☝️ but for Bmore-Responsive https://github.com/CodeForBaltimore/Bmore-Responsive

Task

Identify the types of dashboards needed for the city to use during an emergency.

Acceptance Criteria

• TechSpec updated with research
• PR merged to master with above changes

Task

We need to identify the stakeholders.

Acceptance Criteria

• TechSpec updated with research or new document created with findings
• PR merged to master with above documentation

User Story

As a developer
I'd like to research the use of AWS for this project and the potential costs.
So that I can be confident we're building the best system possible.

Acceptance Criteria

• Documentation regarding AWS solution options
• Documentation regarding Heroku solution options
• Documentation added to the wiki, /docs, or to this ticket.

User Story

As an end user
I'd like to have clear instruction and verbiage instructing use
So that I can use the app effectively

Acceptance Criteria

• User are able to use the product effectively without guidance

Notes

We have a meeting scheduled for Saturday at 5pm.

User Story

As a developer
I'd like to user TravisCI
So that I can ensure tests pass before any code is merged, and auto-deploy as applicable.

Acceptance Criteria

• TravisCI setup for this project
• TravisCI pass is required for merging code into master

Notes

Dependant on #22

User Story

As an end user
I'd like to have a questionnaire page or pop-up or tooltip
So that I can have an easy to access prompt or script to read from when checking-in

Acceptance Criteria

• Page tooltip or pop-up created
• PR merged to master

Notes

Task

Create a hello-world Express app we can build on

Acceptance Criteria

• A hello-world Express app written to best-practices
• PR merged to master with above changes

Notes

We would prefer ES6 syntax.

User Story

As an end user
I'd like to have an account management page
So that I can update my password or other information about myself.

Acceptance Criteria

• User page created
• User page can update user information for only the logged-in user
• PR merged to master with above changes

User Story

As an end user
I'd like to have check-in functionality
So that I can check-in facilities during an emergency

Acceptance Criteria

• check-in functionality built into dashboard
• ability to take notes, and track other stats, via dashboard
• PR merged to master

Notes

This functionality is not currently ready from Bmore-res. Will update ticket when available.

Task

What would trigger this system? What defines an emergency?

Acceptance Criteria

• TechSpec updated with research or new documentation created from findings
• PR merged to master with above changes

User Story

As a user of Healthcare Roll Call, I would like to have the ability to Export Facility Data to a .csv file so that I can quickly review and store data from the system.

Acceptance Criteria

• Allow user to select "Export to CSV"
• All users can export, no disable/denial message
• Browser file DL initiated (browser displays progress/failure/etc)
• 508 compliance, please
• Indicate number of total facilities across all pages

Notes

Eventually the goal will be to have many exports, which is supported by the API. This story address the export of facilities.

Task

Who are the providers and what information do we currently have about them?

Acceptance Criteria

• TechSpec updated with research or new documentation created from findings
• PR merged to master with above changes

Task

Add Codecov to this repo

Acceptance Criteria

• Codecov scans are integrated with repo
• Codecov badge on README

Notes

Dependant on #22 #23

User Story

As a user of Healthcare RollCall, I would like to have my current role displayed, so that I know my security level.

Acceptance Criteria

• The current role of the user is displayed next to or under their userid on each page of the system.
• All documentation is reviewed to ensure that user levels are documented accurately.
• PR merged to master

Notes

related to issue #100 - Adding Security, which has been closed.

Task

Look into what API's BG&E offers for us to hook into to determine power status.

Acceptance Criteria

• TechSpec updated with research or new documentation created from findings
• PR merged to master with above changes

Task

We need to have a detailed overview of the existing system in place and how it is used.

Acceptance Criteria

• TechSpec updated with research or new documentation created from findings
• PR merged to master with above changes

User Story

As a user
I'd like to have filters on the dashboard
So that I can more easily parse entities by their metadata

Acceptance Criteria

• Filters added to dashboard component

Notes

User Story

As a developer
I'd like to Dockerize this project
So that I can use Docker.

Acceptance Criteria

• Dockerfile created
• PR merged to master

User Story

As a developer
I'd like to remove the boilerplate HTML and dependencies
So that I can develop a VueJS front-end without interference and clean up security scans.

Acceptance Criteria

• Default HTML removed
• No security vulnerabilities found
• PR merged to master with the above changes

Notes

Scans by npm or GitHub will show the existing vulnerabilities.

User Story

As an end user
I'd like to have helmet enabled on this site
So that I can be sure we're using a safe site

Acceptance Criteria

• helmet or another package is used to control headers, etc.
• PR merged to master

Task

Look into our ability to use Salesforce CRM as our contact management system.

Acceptance Criteria

• TechSpec updated with research or new documentation created from findings
• PR merged to master with above changes

User Story

As a user
I'd like to be able update contacts or add new contacts
So that I can keep facility contact information up to date.

Acceptance Criteria

• A page to manage individual contacts
• Ability to update a contact or add a contact from the page ☝️
• PR merged to master

Task

Acceptance Criteria

• AC 1
• AC 2

Notes

User Story

As an end-user
I'd like to have a mobile-responsive layout
So that I can use this application from my phone

Acceptance Criteria

• responsive CSS layouts defined
• UX review-approved

Notes

User Story

As a developer
I'd like to have a PostgreSQL database to work with
So that I can develop a data-driven application

Acceptance Criteria

• database diagram added to docs
• any applicable code added
• Docker solution put in place
• PR merged to master if applicable

Notes

Docker is not required but strongly suggested.

User Story

As a developer
I'd like to have good code coverage with unit tests
So that I can ensure the code is clean and functional as changes are made.

Acceptance Criteria

• Codecov reports greater than 80% code coverage
• PR merged to master with unit tests added.

User Story

As a user
I'd like to be able to access this site publically using a public web url
So that I can use the service

Acceptance Criteria

• deploys to Netlify
• Netlify deploys connect to db using environment variables.

User Story

As a developer
I'd like to setup Jest for unit testing
So that I can build clean and working code

Acceptance Criteria

• Jest added to project
• npm test works
• PR merged to master

Notes

An alternative to Jest may be used as long as it works with SonarQube and any CI/CD we use.

User Story

As a developer
I'd like to have docker-compose set up
So that I can set up and build in a single environment

Acceptance Criteria

• one command set up for local development
• backend, frontend, db services can communicate

Notes

Task

It is possible that there are legal statutes that require that providers contact us. We should be aware of any such requirements.

Acceptance Criteria

• TechSpec updated with research or new documentation created from findings
• PR merged to master with above changes

Task

Somewhere down the line, we will need to test the site for 508 compliance. I'm assuming this will be an ongoing process. If you are a developer please keep that in mind.

Acceptance Criteria

• pa11y or other scan returns > 90% 508 compliance
• PR merged to master with any code required to pass compliance requirements

User Story

As a repo user
I'd like to see all documentation in the repo Wiki (other than README's)
So that I can have a clean repo and clean documentation.

Acceptance Criteria

• All items in the docs folder has been converted to the repo wiki

Task

Complete authentication system

Acceptance Criteria

• Store JWT
• Check JWT
• Set up JWT refresh, etc

User Story

As an end user
I'd like to see a dashboard when I login
So that I can be presented with relevant info

Acceptance Criteria

• dashboard system code created
• dashboard page present when user logs in
• PR merged to master

Notes

Dependant on #24

User Story

As an end user
I'd like to have a contact page
So that I can see details about an individual contact

Acceptance Criteria

• contact page created
• contact page pulls from API
• PR merged to master

Notes

The contact endpoints are live in master on Bmore-res

User Story

As a end users
I'd like to have goldenlayout used as a dashboard
So that I can easily see the data I need in a clean format.

Acceptance Criteria

• goldenlayout-vue implemented
• PR merged to master

Notes

https://github.com/emedware/vue-golden-layout
https://golden-layout.com/

User Story

As a user
I'd like to be presented with a login screen
So that I can securely login to the application

Acceptance Criteria

• A login page is created with VueJS
• A user can login using credentials
• PR merged to master

Notes

Dependant on #19 #21 #23

User Story

As an Admin User, I want to be able to Create, Edit and Delete users so that I can manage users within the Healthcare Rollcall system.

Acceptance Criteria

• Limit to ONLY admin users
• Allow admin user to create a new user in the system
  - Following attributes needed to create a new user:
  - Username
  - Email
  - Facility
  - Role
• Allow the new user to receive an email to set password once added to the system
• Allow the admin user to be able to delete user
• Allow the admin user to be able to update user information and save
• Allow the admin user the ability to view list of all users

Notes

User Story

As a user
I'd like to see a map of facilities
So that I can see the status of facilities

Acceptance Criteria

• Basic leaflet map component setup
• Entity color-coded by status (once available).

Notes

User Story

As an end-user
I'd like to consistently see my username on all pages
So that I can interact with the page consistently.

Acceptance Criteria

• Username no longer disappears (unable to recreate except when logging in for the first time or after clearing history)
• When switching to a new user, and logging in, my username is displayed properly. It currently shows the previous username.
• After clearing my history, my username should not be blank when I log in
• PR merged to master

Notes

See msmith125's comment from 5/12/2020 for details and screenshots of system's behavior with the username display.

User Story

As an end user
I'd like to use my stored auth token for API auth
So that I can use the system securely

Acceptance Criteria

• the token is being used for API auth for all required requests
• PR merged to master

Notes

The token is being stored in a cookie thanks to previous work.

User Story

As an end user
I'd like to have a link to reset my password
So that I can recover my password if I forgot it

Acceptance Criteria

• A page to enter new password
• A link to request the new password
• [ ].PR merged to master