Epic Goal

The goal of this Epic is to consolidate, track, and resolve all UI bugs identified by developers during the development and testing of the OpenShift Pipelines Plugin. This centralized tracking will ensure visibility of quality issues, accelerate bug resolution, and improve the overall user interface experience for users interacting with Pipelines, Tasks, Triggers, and related UI components.

Why is this important?

The OpenShift Pipelines Plugin UI is a critical interface for users building and managing CI/CD workflows. Bugs in the UI can lead to:

• User confusion or misinterpretation of status and configuration

• Incorrect results displayed in the UI

• Misleading or inconsistent user interactions

• Degraded developer productivity and user experience

Tracking these bugs in a dedicated Epic ensures that all known issues are addressed systematically, prioritized, and visible across the team, reducing regressions and improving the quality of the plugin’s UI delivery.

Scenarios

This Epic will track all bugs related to UI inconsistencies, defects, or regressions that developers identify during development, testing, or user feedback. Example scenarios include (but are not limited to):

1. Visual inconsistencies — mismatched styles, misaligned elements, incorrect spacing, outdated PatternFly styling.

1. Functional UI bugs — buttons not responding, menus not expanding, broken navigation links.

1. Incorrect headings or labels — content mismatches, missing headers, incorrect section titles.

1. Cross-browser or device specific layout issues — rendering issues on different screen sizes or browsers.

1. Accessibility issues — missing aria labels, poor color contrast, inaccessible UI controls.

1. Regression bugs — previously fixed UI behavior reappearing after new changes.

1. Data display issues — wrong formatting, truncated text, overflow issues in table cells or lists.

Acceptance Criteria (Mandatory)

To mark this Epic as complete:

1. All UI bugs identified by developers during the relevant time period are logged as individual JIRA tickets and linked to this Epic.

1. Each bug ticket should contain:

• • Clear description

• • Steps to reproduce

• • Expected vs. actual behavior

• • Screenshots / screen recordings (where applicable)

• • Severity/priority

• • Environment details (browser, plugin version)

1. All linked bug tickets are triaged and assigned appropriate priority (Critical, High, Medium, Low).

1. All Critical and High priority bugs are resolved and verified by QA or the reporter.

1. UI behavior is tested against updated design standards (PatternFly 6 or other applied UI guidelines).

1. Documentation references are updated if the bug fix changes expected UI behavior or design conventions.

1. CI - MUST be running successfully with tests automated

1. Release Technical Enablement - Provide necessary release enablement details and documents.

Done Checklist

• Acceptance criteria are met
• Non-functional properties of the Feature have been validated (such as performance, resource, UX, security or privacy aspects)
• User Journey automation is delivered
• Support and SRE teams are provided with enough skills to support the feature in production environment