Report a bug

If you believe you've found a bug in PatternFly, we appreciate you taking the time to report it so we can resolve the issue.

1. Check the documentation: First, view the documentation for the component or feature to confirm that the behavior you're seeing is not intentional.
2. Collect clear details: When you file your report, please include the project or product where you noticed the bug and specify any deadlines the fix is needed for. This helps us triage and prioritize.

Find the appropriate repo from the following list. For each repo, first search existing issues to see if your bug has already been reported. If not, open a new issue.

Issues related to PatternFly's visual and interaction design should be contained in the patternfly-design repo.

• Search existing design issues
• Open a new design issue

Bugs that are present only in the React implementation of a component should be contained in the patternfly-react repo.

• Search existing React issues
• Open a new React issue

Bugs that appear in the base HTML/CSS or can be seen in both the React and HTML versions should be contained in the patternfly (Core) repo.

• Search existing Core issues
• Open a new Core issue

For bugs found in a PatternFly extension, please file the issue in that extension's specific repository:

• chatbot: Code for the ChatBot extension.
• patternfly-quickstarts:. Code for the quick starts extensions.
• react-catalog-view: Code for the catalog view extension.
• react-component-groups: Code for the component groups extension.
• react-data-view: Code for the data view extension.
• react-log-viewer: Code for the log viewer extension.
• react-topology: Code for the Topology extension.
• react-user-feedback: Code for the user feedback extension.

Bugs related to the PatternFly.org website or its documentation should be contained in the patternfly-org repo.

• Search existing website issues
• Open a new website issue