As a stakeholder at the CDC, I want to view ReportStream OKR product metrics on a user-friendly dashboard (without requiring special permissions to access) that allows intuitive filtering and data analysis.
Description/Use Case
Now that we are able to obtain and log events within the UP and have proven the possibility to import that stored data into PowerBI, this ticket aims to create the user-facing OKR Metrics Dashboard based on the design brief, which was defined in #12450.
Risks/Impacts/Considerations
The dashboard is limited to the data that is provided; therefore, there is no existing data at this time (until it is backfilled) that precedes the logging work that was recently completed. The output visualizations within the dashboard may have insufficient historical data to produce long-term graphs, but will improve over time as more data is logged and synced.
Once we move the instance outside the staging storage environment. We must consider which sensitivity label to assign the dashboard and reports - whether it's the following and how the more restricted label may prevent access:
General (default): data not meant for the public
Restricted Use: sensitive data not meant for the public
Some unknown barriers can be:
frequency of data refresh to PowerBI and thus the connected online dashboard
load time/ performance of the interactive elements (e.g., filtering by condition) within the online dashboard
support for different internet browsers (optimizing design on Chrome at this time)
jsutantio
commented
7 months ago
User Story
As a stakeholder at the CDC, I want to view ReportStream OKR product metrics on a user-friendly dashboard (without requiring special permissions to access) that allows intuitive filtering and data analysis.
Description/Use Case
Now that we are able to obtain and log events within the UP and have proven the possibility to import that stored data into PowerBI, this ticket aims to create the user-facing OKR Metrics Dashboard based on the design brief, which was defined in #12450.
Risks/Impacts/Considerations
The dashboard is limited to the data that is provided; therefore, there is no existing data at this time (until it is backfilled) that precedes the logging work that was recently completed. The output visualizations within the dashboard may have insufficient historical data to produce long-term graphs, but will improve over time as more data is logged and synced.
Once we move the instance outside the staging storage environment. We must consider which sensitivity label to assign the dashboard and reports - whether it's the following and how the more restricted label may prevent access:
Some unknown barriers can be:
Dev Notes
Starting point for data refresh
Acceptance Criteria