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

Pipeline Overview - Error Banners for API failures

XMLWordPrintable

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

      None

      Show
      None
    • False
    • Release Note Not Required
    • Pipelines Sprint CrookShank 43, Pipelines Sprint CrookShank 44

      Story

      As a user, I want to see a Error Banners in Pipelines Overview page so I know the appropriate API errors or Data load issues clearly.
      Each card component in the page needs to display a error banner with clear message when it failed to load respective data.

      Background

      In current view the User doesn't have a clear indication if an error occurred in while loading the data for the card components in pipeline overview page

      Out of scope

      • Backend API changes
      • UX modifications for the error banner

      Approach

      • Display an error banner in each of the card component when the API fails.
      • Mention appropriate message so that the user can understand.
      • Hide error messages if the API data is fetched in subsequent requests succesfully.

      Dependencies

      None

      Acceptance Criteria

      • Error banner is displayed in Pipelines Overview page.
      • Each card component in the page displays a separate error banner when it's respective data load fails from API.
      • Error banner is removed and respective data/chart is displayed after data is loaded.

      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
      • All acceptance criteria met

              rh-ee-arvkrish Arvind Krishnamurthy
              rh-ee-arvkrish Arvind Krishnamurthy
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: