Make annual limits and current usage status visible to users in the UI

yaelberger-commits commented 1 month ago

Description

As a user, I need to be able to see my annual limits and current usage status in the UI of my service so that I can stay within the hard annual limits of GC Notify.

WHY are we building? Clients cannot see their annual limits or their current usage status. To calculate their usage, clients have to manually sum up month over month statistics. We also don’t enforce the annual limits, so clients have no incentive to honour them. WHAT are we building? Changes to the UI and Dashboard VALUE created by our solution

Users feel confident about budgeting their message usage. Metrics: Sentiment score, number of users who max out their usage before fiscal, how early users max out their usage
Users feel that they are given appropriate degree of warning before reaching their annual limit. Metrics: Sentiment score, number of users who max out their usage before fiscal, how early users max out their usage
Users are not able to send messages after reaching their annual limit. Metrics: Backend data

Documentation and Artifacts

PRD https://docs.google.com/document/d/1qoqzKzt4mXQh1NPtZE_GBqsN0D87wnTbHVNIBRu75D0/edit

Acceptance Criteria

[ ] Dashboard: show usage tracker (display as a number or progress bar). Combine this with daily usage tracker.
[ ] Annual usage page (previously called messages sent): re-design this page to show annual usage tracker (display as a number, progress bar, and/or graph)
[ ] Because annual limits roll over a longer period, we can help users track in smaller increments such as quarters or months. This can help them budget and manage their usage
[ ] Cypress UI tests if needed.
[ ] Generate appropriate log messages so that executions of this feature can be tracked
[ ] Can misuse of this feature cause harm? If yes, create an alert
[ ] Update the status of related findings, insights, and hypotheses on the Research Airtable
[ ] Once change/fix/feature is implemented, link relevant Airtable records to design artifacts (Figma)
[ ] Does the feature change our Information Architecture? If so, update the Sitemap in En/Fr
A11y
Bilingualism
Privacy considerations
Security controls in place
Measuring success and metrics