-
Epic
-
Resolution: Done
-
Critical
-
None
-
ACM Build a Catalog-Experience from our PolicyCollectionRepository (phase 1)
-
False
-
None
-
False
-
To Do
-
ACM-1395 - ACM Build a Catalog-Experience for Policy-Collection-Repository
-
-
0% To Do, 50% In Progress, 50% Done
Epic Goal
- goal is to work on a design how this can be implemented
Why is this important?
- improving user, adoption, setting up policies from PolicyCollectionRepo is not accepted by all Customers
- Enhance the ACM Governance first time customer experience. Not just for on-prem, but also for configuration management on cloud in the future.
Scenarios
- ...
Acceptance Criteria
- CI - MUST be running successfully with tests automated
- Release Technical Enablement - Provide necessary release enablement details and documents.
- in a meeting we agree on the design and after that we start with implementation
Dependencies (internal and external)
- ...
Previous Work (Optional):
- …
Open questions::
- …
Done Checklist
- CI - CI is running, tests are automated and merged.
- Release Enablement <link to Feature Enablement Presentation>
- DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
- DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
- DEV - Downstream build attached to advisory: <link to errata>
- QE - Test plans in Polarion: <link or reference to Polarion>
- QE - Automated tests merged: <link or reference to automated tests>
- DOC - Downstream documentation merged: <link to meaningful PR>
