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

Add "Paid Status <year>" column to User Account Management table #36

Open
ryanprince opened this issue Oct 20, 2018 · 0 comments
Open

Comments

@ryanprince
Copy link
Contributor

Administrators have a table overview of users in the system inside their User Account Management screen. This change is to add a Paid Status column to it.

screen shot 2018-10-20 at 1 59 30 pm

Description

Expected Behavior

  • Title should be “Paid Status ”, where the year is a drop-down with the options being all years from the allYears array from the years api. The default value should be the currentYear from the years api.
  • Should add only one server request for loading the data. The route /api/payments_documentation uses an accountId, and retrieves documentation only for that account's payments; a new route should be added for getting all account documentation for all users. A new route is preferred over making the accountId optional for the original route, since it would simplify making this route admin-only. However, the admin-only route and the original route could call the same getPaymentsDocumentation() function to do the MongoDB request.
  • The rows' text should be either “-“, “Needs Action,” “Exemption Requested”, “Exemption Rejected”, “Exempt”, or “Paid”. “-“ should have the default text style, “Exemption Requested” should be made to stand out, “Exempt” and “Paid” should have Bulma's success style, and “Needs Action” and “Exemption Rejection” should have Bulma's warning style.

Context

Administrators will use this column to feel confident that they've received all the payments that they should have for the current year. They'll expect to still have access to the data / the data shouldn't disappear when the next year begins, which is why the year value should be selectable. During the year, the column will help administrators follow up with users about payments that are due, and to find exemption requests that need action from them.

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

No branches or pull requests

1 participant