Background/Feature Origin

This feature builds on RHDHPLAN-311, which introduced a data summarization scorecard that can be added to the homepage, and a data caching mechanism to collect data for display. This capability needs to be extended to be more configurable and more actionable, taking users to see those entities which may need attention.

Why is this important?

This feature is important because it allows Engineering Managers and Product Managers to quickly assess the overall technical health, compliance, and risk of all applications or components owned by their team/group, eliminating the need to manually check each service's individual scorecard. This consolidated, high-level summary is essential for managerial oversight and risk identification in large organizations.

User Scenarios

• Engineering Manager / Platform Engineer: I want to define, name, and view aggregated KPIs across all applications or components owned by my team/group, so I can quickly assess overall technical health, compliance, and risk without manually checking each service's individual scorecard.

Dependencies (internal and external)

The feature relies on:

• The existing data summarization scorecard functionality introduced in RHDHPLAN-311.
• The existing data caching mechanism.
• The accurate and consistent definition of Owner/Group entities and Group-Component relationships in the Software Catalog.
• Existing data sources already integrated with the RHDH Scorecard plugin.

Acceptance Criteria

Release Enablement/Demo - Provide necessary release enablement details
and documents

DEV - KPI Configuration: The Scorecard configuration interface includes an option to create an "Aggregated KPI," allowing Platform Engineers to define metrics that sum or average results across multiple entities.

DEV - Customizable Name/Description: A Platform Engineer can provide their own name and description for a newly created KPI so the metric can be easily understood by end-users.

DEV - Upstream code and tests merged: <link to meaningful PR or GitHub
Issue>

DEV - Upstream documentation merged: <link to meaningful PR or GitHub
Issue>

DEV - Downstream build attached to advisory: <link to errata>

QE - Test plans in Playwright: <link or reference to playwright>

QE - Automated tests merged: <link or reference to automated tests>

DOC - Downstream documentation merged: <link to meaningful PR>