Implementation: expanded rows for different aggregated/concatenated reports or report-reports

[RomijnHumanoids]

About this feature

Detailed description

Implementation ticket for #3485 to view expanded row of information about all the different kinds of reports from as simple as 'one object x one report type' to aggregated reports based on reports. The design in Figma sums what to show for each possible composition.

Feature benefit/User story

Consistency and overview in all the different reports and their sub reports directly from the reports page history tab.

As a user, I want to expand rows of reports so that I can identify the report and understand the scope, possibly digging deeper in its sub reports page.

Specifications

The implementation should include…

• Column for 'input objects' now functions as 'input' because reports' input is possibly other reports instead of objects.
• Expanded row for composition 1:
  Scope: Intern
  Types: 1 report type
  Input: 1 input object
• Expanded row for composition 2:
  Scope: Intern
  Type(s): 1 report type
  Input: Multiple input objects
• Expanded row for composition 3:
  Scope: Intern
  Types: Multiple report types
  Input: Multiple input objects
• Expanded row for composition 4:
  Scope: Intern/extern
  Types: 1 report type
  Input: Multiple reports
• Expanded row for composition 5:
  Scope: Intern/extern
  Types: Multiple report types
  Input: Multiple input reports
• Expanded row for composition 6:
  Scope: Sector/extern
  Type(s): 1 report type
  Input: Multiple input reports
• Expanded row for composition 6:
  Scope: Sector/extern
  Type(s): Multiple report types
  Input: Multiple input reports

Additional information

Figma file should speak for itself. If there are any questions please be in touch.

Design

Screenshots

Include screenshots of the proposed design changes here.

Figma link

https://www.figma.com/design/GJCDuJYinANHYQ6Ystfzgn/%E2%9C%8D%F0%9F%8F%BC-KAT-%7C-For-Review-%7C-Reports-Page?node-id=1677-3&t=GkdbP8rUqObAEgI6-1

Implementation

This part should only be filled in by the developers.

Possible solution

Outline your proposed solution for implementing the feature. You can include any specific ideas, designs, or functionalities here.

Alternatives considered

Describe any alternative approaches or solutions you've considered, and why you believe the proposed solution is superior.