Epic Goal

• Provide a better onboarding-experience. Customer get an entry point where they can select a list of best-practises policies
• they also have the option to connect to a git-repository and retrieve some policies

Why is this important?

• Help guide the user to creating their first policy, drive better adoption
• not all Customers like to use the way to deploy policies from Policy-Collection-Repository

Scenarios

1. see some proposals from the design-team

I'm fine with this approach: https://marvelapp.com/prototype/64bgi6b/screen/88253483

Acceptance Criteria

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.
• we need a meeting where all stakeholders agree

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. https://marvelapp.com/prototype/94f69jg/screen/87313583
2. https://docs.google.com/presentation/d/1bVIU0CweyomPqe6Z7hvq2JSfkri1UnLrdWTw2D0Ak_c/edit#slide=id.p

Open questions::

1. we need a meeting where all stakeholders agree

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>