codeforkansascity/cmr-clinic

cmr-clinic's Issues

Persisted State not working as should

When page is refreshed the data disappears. I don't believe the configuration for vue-persistedstate is correct for nuxt.

User cannot determine if charge has not been marked for eligibility, is not eligible, or is eligible

Please suggest then implement a UI that would allow a user to understand if the Convicted, Eligible, and Expunge flags have NOT been set or have been set to false. It is obvious when it is set to true by the checkmark.

The criminal history may be entered by one person, and another one my review the history to determine what is or is not eligible.

When the user looks at the following screen they can to tell if:

• someone has not set the eligibility for the charge
• someone has determined and marked it Not eligible

This also applies to Convicted and Expunge.

Determine best way to version API enpoints

When the backend changes it's API we need an easy way to have different versions of the front end to use the correct version of the API.

For example pagination to the Applicant, the grid is being changed to pass back pagination information as well as data. The current version is only passing back data.

Determine if we need to flatten out data in the VueX Store

Background:

In the past, there were issues with the reactivity of the convictions and possibly charges. This was caused them being nested in inside of client.
This was solved by two things

1. Moving convictions to the root of the VueX store
2. Using Vue's set()

Questions:

1. Should we move charges to the root of the VueX store?
2. Is the current code updating the DOM correctly?
3. What code pattern should we be using?

Find good Date Picker for input-date

in components/input-date.vue there is a standard text input.
We tried HTML 5 type date, but it did not work on all browsers.

Preferably it would save the date in a format that MySQL date type would except.

Currently input-date is being used in the section-persons-information.vue Date of birth and Expiration date.

It also needs to be added to input-conviction-fields.vue Release Date

Change Applicant Status to Summary, then create a true status field.

Change Applicant Status to Summary

During expungement day users needed to leave more information about the status of an applicant that they were working on that would fit in a word or two. They used that status field to communicate the current state or what needed to happen next to the applicant.

• Backend changes
• Rename status field to summary.
• Rename Status label to Summary

Determine the best way to merge code into formal releases

Currently, the develop branch contains everything that will be in the next release, and pushed into master.

We need a way for people to work on issues, test them locally with the proposed code base for the next release, as well as give our users a place to QA the release before we push it to the live site.

View - Convicted, Eligible, PleaseExpunge - are incorrect

These always show, even if they are not selected.

Do not allow the Expunge flag to be set unless Eligible is set to yes

In the following screen snipit, the user should not be able to set Expunge.

The component with the charge fields is input-charge-fields.vue

Setup permissions for users

At this time we think we will have the following types of users:

• Clinic User - Has almost all permissions
• Volunteer Lawyer - Cannot add or delete an Applicant/Client, but can
  • edit Applicant/Client
  • add, edit, remove convictions, charges, and service

• Work with backend developers to determine how to pass the user's role.