Uploaded image for project: 'RH Developer Hub Planning'
  1. RH Developer Hub Planning
  2. RHDHPLAN-915

Users can drill down from aggregated Scorecards to related entities

Create Doc EPIC from R...Prepare for Z ReleasePrepare Test Plan (Y R...XMLWordPrintable

    • False
    • Hide

      None

      Show
      None
    • False

      Feature Overview (aka. Goal Summary)

      This feature builds on existing Scorecard features, to better understand and take action from the data displayed by Scorecard.

      The current lack of transparency in aggregated KPIs creates a significant barrier to operational efficiency, as managers can monitor high-level health scores but cannot access the granular data behind them. This "black box" effect prevents the identification of specific underlying services or components that are negatively impacting the overall score, leading to increased manual effort and delayed response times. By implementing a drill-down capability, the scorecard would transition from a passive reporting tool to an actionable diagnostic interface, allowing leadership to instantly connect high-level metrics to the individual contributors driving those values. This transparency is essential for validating the accuracy of the data and ensuring that stakeholders can pinpoint exactly where interventions are needed to improve organizational performance.

      Goals (aka. Expected User Outcomes)

      • Engineering Manager / Platform Engineer: When looking at a scorecard, I want to know how recent the data is, and be able to drill down from the card into the entities it represents, to better understand and troubleshoot the underlying data, and take action when needed.

      Requirements (aka. Acceptance Criteria):

      1. Drill-Down Capability: As a Manager, I want to be able to click on an Aggregated KPI to see a list of the individual components that contributed to the value, so I can identify the underlying services impacting the overall score. (Figma)
      2. Visible Data Freshness: To help provide users with sufficient context, each scorecard should include a timestamp showing when its displayed data was generated (if it's pulled from cached data)

      Out of Scope (Optional)

      • Linking out to the underlying system of record that Scorecard is pulling from (eg a Jira filtered issue list page)

      Customer Considerations (Optional)

      •  

      Documentation Considerations

      • Update the existing RHDH documentation clearly explaining how to utilize the drill-down function.

       

              rh-ee-imykhno Ihor Mykhno
              jfargett@redhat.com Christophe Fargette
              Shiran Hirshberg
              RHDH Plugins
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: