Major CUSTOMER PROBLEM
RHACS lacks ability to filter Violations using labels. This will help customers view deployments based on application labels. This will also help integration tools such as RHACS Plugin for RHDH/Backstage to provide violation information for a specific application in RHDH.
USERS
This section should specify the intended user of the set of features specified in this epic and should link out to this page for a description of personas
ACCEPTANCE CRITERIA
- CI - MUST be running successfully with tests automated
- Release Technical Enablement - Provide necessary release enablement details and documents.
- ...
QUESTIONS
This section should specify what questions we are trying to answer for the customer with this set of features.
ACTIONS
This section should specify what actions we are trying to enable the user to take with our product.
CONSIDERATIONS
This section may contain notes about any number of things that should be taken into consideration when building out this set of features, including (but not limited to) intended future direction for these features or for the corresponding feature family.
UX/UI
Generally mocks should be attached to individual stories. However, if mocks combine multiple individual stories in order to enable the best user interaction, then the mocks should be linked here and this section should denote which stories are encompassed by the mocks.
DELIVERY PRIORITY
This section should outline the desired order of delivery for stories comprising this epic. For example:
