Task

1. Important to understand how the redirect to the page with all individual components that contributed to the homepage aggregated scorecard page will works (Figma);
2. As we already get entities owned by user ownership during aggregation, should we try to reuse it to prevent extra calculation for this new endpoint? 
3. It is necessary to take into account that the endpoint must support the following capabilities:
   1. Return entities related to selected provider (eg. github.open_prs) entities;
   2. Support to return the following information (columns) about entity: Entity Name, Who is owner, Entity Kind, Time when the scorecard sync happened for the metric, Score (need to ask PMs expectation from this column) (Figma);
   3. Support pagination for table where entities displayed;
   4. Support displaying rows change (by default 5 row);
   5. Support column sorting for table where entities displayed;
   6. [Need to clarify in PMs] Support entity filters.
4. Should be returned threshold for the chart or not? 
5. Which error theoretically can happened and how it will be thrown.

Background

Add ability to click on an Aggregated KPI to see a list of the individual components that contributed to the value, it can help identify the underlying services impacting the overall score. (Figma)

Dependencies and Blockers

QE impacted work
Documentation impacted work 

Acceptance Criteria

• Understand how the logic should work;
• Agree with Fronted team:
  • Endpoint path;
  • How filters can be added to the request;
  • How many endpoints needed;
  • Possible errors can be thrown; 
  • The response object type will be.