Compliance Framework Report tabs
What does this MR do and why?
This MR builds on the initial setup work completed in Compliance Framework Report feature flag and fo... (!110472 - merged)
Adds new top level reports_app component to house the existing + new reports. Move feature flag logic into this new component. Add new (mostly empty) framework report component to be expanded upon in future MRs.
Add tabs to allow switching between the existing Compliance Violations report and the new Compliance Framework report. Extract shared report header component to be reused by both.
Changes the way filter query params are parsed so that it happens inside each specific report, instead of in the top level init code. This means each report knows about their own params but not each others, and means that the params will be (re)parsed when switching tabs.
Also moves a bunch of specs into a subfolder, to match the directory structure of the components.
Note that the tabs are hidden behind development feature flag compliance_frameworks_report and should stay so for several more MRs.
Screenshots or screen recordings
| FF enabled, existing report | FF enabled, new report | FF disabled |
|---|---|---|
 |
 |
 |
How to set up and validate locally
- Browse to a Group -> Security & Compliance -> Compliance Report
- There should be no visible changes when feature flag is disabled
- There should be new tabs when the feature flag is disabled. The new "Frameworks" tab has empty content at this stage.
Feature.enable(:compliance_frameworks_report)
Feature.disable(:compliance_frameworks_report)MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.
Related to #387910 (closed)