-
Epic
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
None
-
V4.18 PatternFly component group implementation
-
False
-
None
-
False
-
Not Selected
-
To Do
-
43% To Do, 0% In Progress, 57% Done
Document with all migrated components and potential candidates:
https://docs.google.com/spreadsheets/d/15jtfdjgAZZf3F8jtdCcrsJ-YeygZWDale7j4x7xLWEQ/edit?usp=sharing
–
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
- Goal of this epic is to capture the stories that will cover implementation of PatternFly's component-groups components, which are moved into PF from console-shared package
Why is this important?
- Console needs to re-implement its moved components
- We need to offload console repository of any components that might be reusable in other projects
Scenarios
- ...
Acceptance Criteria
- CI - MUST be running successfully with tests automated
- Release Technical Enablement - Provide necessary release enablement details and documents.
- ...
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>
- clones
-
CONSOLE-3951 PatternFly component group implementation
- Dev Complete