You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
The text was updated successfully, but these errors were encountered:
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.
Description
Expected Behavior
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.
The text was updated successfully, but these errors were encountered: