Uploaded image for project: 'OpenShift Pipelines'
  1. OpenShift Pipelines
  2. SRVKP-9625

Update page and section headings for Pipelines, Tasks and Triggers Page

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Normal Normal
    • Pipelines 1.23.0
    • None
    • UI
    • None
    • Pipelines Sprint CrookShank 44

      Story

      To ensure consistent and maintainable styling on the Pipelines, Tasks, and Triggers page, I want to migrate all CSS for headings from PatternFly 5 to PatternFly 6 standards so that our UI aligns with the latest design system, eliminates styling regressions, and improves maintainability.

      Background

      On the Pipelines, Tasks, and Triggers page, the headings are styled using PatternFly 5 CSS classes/variables. These must be updated so they remain visually correct and semantically consistent with PatternFly 6. This will eliminate visual bugs or regressions for users navigating these key UI sections.

      Out of scope

      • Global migration of all CSS across the entire product (only headings on the Pipelines, Tasks, and Triggers page).
      • Functional changes to components outside of styling (e.g., JavaScript/UX logic).
      • Full redesign of the page layout or UX — only CSS migration for headings.
      • Content rewriting for the page’s textual information.

      Approach

      • Identify all CSS applied to page and section headings on the Pipelines, Tasks, and Triggers page.
      • Ensure it is aligned properly after updating the dependencies to PF6

      Acceptance Criteria

      • All PatternFly 5 CSS references for page and section headings on the Pipelines, Tasks, and Triggers page are removed or replaced with PatternFly 6 equivalents.
      • Headings render visually correct with PatternFly 6 styling and align with design expectations.
      • No visual regressions occur due to stale CSS overrides or outdated variables.

      INVEST Checklist

      Dependencies identified

      Blockers noted and expected delivery timelines set

      Design is implementable

      Acceptance criteria agreed upon

      Story estimated

      Done Checklist

      • Code is completed, reviewed, documented and checked in
      • Unit and integration test automation have been delivered and running cleanly in continuous integration/staging/canary environment
      • Continuous Delivery pipeline(s) is able to proceed with new code included
      • Customer facing documentation, API docs etc. are produced/updated, reviewed and published
      • Acceptance criteria are met

              rh-ee-arvkrish Arvind Krishnamurthy
              rh-ee-apalit Anwesha Palit
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: