https://docs.google.com/spreadsheets/d/15jtfdjgAZZf3F8jtdCcrsJ-YeygZWDale7j4x7xLWEQ/edit?usp=sharing

Epic Goal

• Goal is to locate and replace old custom components with PatternFly components.

Why is this important?

• Custom components require supportive css to mimic the visual theme of PatternFly. Over time these supportive styles have grown and interspersed through the console codebase, which require ongoing efforts to carry along, update and maintain consistency across product areas and packages.
• Also, custom components can have varying behaviors that diverge from PatternFly components, causing bugs and create discordance across the product.
• Future PatternFly version upgrades will be more straightforward and require less work.

Acceptance Criteria

• Identify custom components that have a PatternFly equivalent component.
• Create stories which will address those updates and fixes
• Update integration tests if necessary.

Open questions::

1. …