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

Update “Last weeks” Label to “Last week” and Align Payload Accordingly

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Major Major
    • Pipelines 1.21.0
    • None
    • UI
    • 2
    • False
    • Hide

      None

      Show
      None
    • False
    • Hide
      Updated “Last weeks” Filter Label for Clarity
      The time-range filter previously labeled “Last weeks” has been updated to “Last week” to avoid ambiguity. The corresponding API payload has been aligned with the new label to ensure consistent behavior and improve usability (as reported by Ford).
      Show
      Updated “Last weeks” Filter Label for Clarity The time-range filter previously labeled “Last weeks” has been updated to “Last week” to avoid ambiguity. The corresponding API payload has been aligned with the new label to ensure consistent behavior and improve usability (as reported by Ford).
    • Enhancement
    • Proposed
    • Pipelines Sprint Pioneers 43

      Story

      As a user selecting time-range filters on the Pipeline Overview dashboard
      I want the label to clearly reflect the actual time range being applied
      So that the filter is intuitive, unambiguous, and accurately represented in both UI and API payloads.


      Background

      The existing label “last weeks” is unclear and has caused confusion for customers who expected a single-week range. The payload also sends a pluralized range that does not match the intended behavior. Updating the label to “Last week” requires adjusting the corresponding payload to reflect the correct time range.


      Out of Scope

      • Changes to other date-range labels.
      • Backend API modifications.
      • UX redesign of the filter component.

      Approach

      • Update the label from “Last weeks” to “Last week” in the time-range dropdown.
      • Update the associated filter payload to send the correct 7-day range.
      • Ensure UI and backend interpretation remain aligned.
      • Add tests validating both label change and payload accuracy.

      Dependencies

      • Console UI time-range component
      • Tekton Results summary API (consumes the updated payload)

      Acceptance Criteria

      • Label displays as “Last week” in all relevant UI components.
      • Payload sends the correct single-week range.
      • No regressions in other time-range filters.
      • Automated tests validate label, payload, and API interaction.

      INVEST Checklist

      • Dependencies identified
      • Story implementable
      • AC agreed upon
      • No blockers
      • Story estimated

      Done Checklist

      • Code updated, reviewed, documented, and checked in
      • Unit and integration tests added and passing in CI
      • No regressions in other filters
      • Documentation updated
      • All acceptance criteria met

              rh-ee-apalit Anwesha Palit
              rh-ee-apalit Anwesha Palit
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: