Major Feature Overview
Enhance the Policy dashboards to better support customizations around annotations / labels.
The current UI forces the UX around the "Standards", "Categores", "Controls"; which maps to NIST grouping hierarchy. However, not all customers use Policy feature for compliance reasons, and would prefer control over the UX to fit their use cases (e.g. orient dashboard around environment - dev, stage, prod; etc)
Previous work:
UXD: ACM Data Table Feature Enhancement (Legacy)
Attached screenshots
Goals
This Section: Provide high-level goal statement, providing user context
and expected user outcome(s) for this feature
- Allow users to provide custom annotations on policy resources
- Allow users to provide custom labels on policy resources
- Allow users to be able to filter by custom annotations / labels
- Allow users to be able to create custom columns based on annotations / labels
Requirements
This Section: A list of specific needs or objectives that a Feature must
deliver to satisfy the Feature.. Some requirements will be flagged as MVP.
If an MVP gets shifted, the feature shifts. If a non MVP requirement slips,
it does not shift the feature.
| Requirement | Notes | isMvp? |
|---|---|---|
| CI - MUST be running successfully with test automation | This is a requirement for ALL features. |
YES |
| Release Technical Enablement | Provide necessary release enablement details and documents. |
YES |
(Optional) Use Cases
This Section:
- As a user, I can provide supplementary annotations and labels in the Create / Edit Policy wizards
- As a user, I can see all annotations and labels for a Policy in the policy table and details page
- As a user, I can filter the Policy overview dashboard by any combination of annotations and labels
- As a user, I can filter the Policy table by any combination of annotations and labels
- As a user, I can construct a custom column based on a label or annotation
Questions to answer
- How to support custom columns based on labels or annotations?
- Where can this configuration be stored?
- Is this per user, or global?
Out of Scope
- …
Background, and strategic fit
This Section: What does the person writing code, testing, documenting
need to know? What context can be provided to frame this feature?
Assumptions
- ...
Customer Considerations
- ...
Documentation Considerations
Questions to be addressed:
- What educational or reference material (docs) is required to support this
product feature? For users/admins? Other functions (security officers, etc)? - Does this feature have a doc impact?
- New Content, Updates to existing content, Release Note, or No Doc Impact
- If unsure and no Technical Writer is available, please contact Content
Strategy. - What concepts do customers need to understand to be successful in
[action]? - How do we expect customers will use the feature? For what purpose(s)?
- What reference material might a customer want/need to complete [action]?
- Is there source material that can be used as reference for the Technical
Writer in writing the content? If yes, please link if available. - What is the doc impact (New Content, Updates to existing content, or
Release Note)?
