Skip to content

Resolve "[Frontend] Allow filtering compliance violations by branch"

Illya Klymov requested to merge 358414-frontend-allow-filtering-compliance-violations-by-branch into master

What does this MR do and why?

This MR introduces filtering to compliance framework report

Screenshots or screen recordings

Desktop:

image

Mobile:

image

Demo:

Compliance_report___Commit451___GitLab__1_

How to set up and validate locally

  1. Ensure you have valid EE license
  2. Switch to xanf-fix-compliance-violations branch. This branch contains fixes for seeder which greatly simplify testing (or master if Fix compliance violation seeder (!117942 - merged) is already merged
  3. Run FILTER=compliance_report_violations rake db:seed_fu to seed compliance report violations
  4. Switch to this branch 358414-frontend-allow-filtering-compliance-violations-by-branch
  5. Open /groups/Commit451/-/security/compliance_dashboard/violations in your GDK (assuming you have default Commit451 group)
  6. If you see "no violations" by default - this means you failed to seed DB properly take a closer look to first 3 steps
  7. Observe Search target branch filter, use master to check if it is filtering

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Related to #358414 (closed)

Edited by Illya Klymov

Merge request reports