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
As an Aspects Product Manager, I want detailed wireframes completed for in-context metrics on the Studio Outline and Unit pages, so that the delivery team and product are all aligned on how this feature will look and behave.
Acceptance Criteria
It must be clear to Studio users when in-context metrics are available for them to view for a given section, subsection, unit, and component since not all sections, subsections, units, and component types will have in-context metrics available
In-context metrics are to be hidden by default, but easily accessed and re-hidden by the user.
When visible, the user must be able to view the in-context metrics next to/by the content the metrics relate to.
Default metrics that are shown must be tailored to the type of content displayed.
Default metrics for this initial release are available for problem and video components and graded subsections with learner engagement.
If a course is re-run, the course metrics are copied over from the copied run. By default, the new course run or imported course does not show the copied course metrics, but users are able to view historic (copied) run metrics in-context if they choose. (There must be a place in the UI that makes this option clear and changeable).
The visuals can be viewed without having to zoom or scroll horizontally (the sidebar is wide enough to clearly display visualizations in-full with legible labels and without distortion)
Note: This feature is expected to be used primarily by users on desktop (resolution would need to work for a small desktop screen, but that would be the smallest we’d need this to work at this point).
The text was updated successfully, but these errors were encountered:
User Story
As an Aspects Product Manager, I want detailed wireframes completed for in-context metrics on the Studio Outline and Unit pages, so that the delivery team and product are all aligned on how this feature will look and behave.
Acceptance Criteria
The text was updated successfully, but these errors were encountered: