Epic Goal

Improve the Pipeline Overview page to address customer-reported issues around data loading, accuracy, and usability, ensuring a more stable and intuitive experience.

Why is this important?

Customers reported degraded reliability and confusing behavior on the Pipeline Overview page, including stale data, unclear filter labeling, and missing feedback during data fetch. These issues directly impact trust in the dashboard and hinder debugging and observability workflows. This epic ensures the page behaves consistently, surfaces failures clearly, and reflects accurate Tekton Results data at all times.

Scenarios

• As a user, I want to see a loading indicator so I know the dashboard is actively fetching data.

• As a user, I want errors to be visible immediately when API calls fail.

• As a user, I want confidence that data shown is fresh and not cached incorrectly.

• As a user, I want the time-range filters (“last week”, “last month”, etc.) to be intuitive and accurate.

• As a user, I want my selected filters to persist when I navigate across different OCP console tabs.

Acceptance Criteria (Mandatory)

• A loading spinner is displayed whenever API data is being fetched.

• An error banner is shown on any API or data-load failure.

• Logic is implemented to prevent stale or cached data from being rendered.

• API timeout can be configured and is increased safely (e.g., from 60s to 90s) if needed.

• “Last weeks” label is updated to a clearer label (e.g., “Last week”), and payload changes reflect the new range.

• Filter selections persist seamlessly when navigating between OCP tabs.

• CI MUST be running successfully with automated tests covering the updated behavior.

• Release Technical Enablement MUST be provided, including documentation of UI changes and any API usage changes.

Dependencies (Internal and External)

• Tekton Results backend availability and API stability.

• Console plugin framework routing and state-persistence behavior.

• OCP UI global navigation events that may refresh state.

• Coordination with QE for test updates.

• Console UX team for label and terminology validation.

Previous Work (Optional)

• Initial implementation of Pipeline Overview dashboard.

• Previous fixes related to filter payloads and date-range handling.

Open Questions

• Should timeout be fully user-configurable or fixed at 90s?

• Should we introduce caching invalidation heuristics or always hard-refresh?

• Do we need UX approval for the updated “Last week” label and any other terminology changes?

Done Checklist

• All acceptance criteria are met.

• Non-functional requirements validated: performance, resource usage, UX clarity, security/privacy.

• User Journey automation delivered for the updated Pipeline Overview workflow.

• Support and SRE teams have required knowledge and documentation to manage this feature in production.