-
Epic
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
None
-
Lightspeed integration
-
False
-
None
-
False
-
Not Selected
-
To Do
-
0% To Do, 0% In Progress, 100% Done
OCP/Telco Definition of Done
Epic Template descriptions and documentation.
<--- Cut-n-Paste the entire contents of this description into your new Epic --->
Epic Goal
- Enable console users to use the OpenShift LightSpeed plugin
Why is this important?
- Console users should have access to LightSpeed plugin and its functionality
Scenarios
Pre Lightspeed Install
- LightSpeed Button becomes visible to all users no matter what the RBAC is
- If user has access to install, We show them how and or link to Operator
- If you user doesn’t have access to install, We tell them to Contact Admin and request them to install the LightSpeed Service
- Console Setting will be added to disable the button for all by Admins only
Post Lightspeed Install
- User Preference added to hide LightSpeed button
Acceptance Criteria
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>