Skip to content

Add operational vulnerability empty state

Alexander Turinske requested to merge 340342-operational-empty-state into master

What does this MR do and why?

Add operational vulnerability empty state

  • add additional configuration links
  • generalize not-confugired empty state to work for operational vulnerabilities
  • update tests

How to set up and validate locally

  1. Upload a GitLab Ultimate license
  2. Enable the :operational_vulnerabilities feature flag
  3. Navigate to a project with security scans enabled
  4. Navigate to Security & Compliance => Vulnerability Report and verify the page
  5. Navigate to a group with security scans enabled
  6. Navigate to Security & Compliance => Vulnerability Report and verify the page
  7. Navigate to Menu => Security => Vulnerability Report and verify instance vulnerability report page

Screenshots or screen recordings

Page Before After
Project - Sec Dash - Unconfigured project_-sec_dash-_un No visual change
Project - Dev tab - Unconfigured project-un No visual change
Project - Dev tab - Configured proj-dev-con No visual change
Project - Op tab - Unconfigured Empty tab proj-op
Group - Dev tab - Unconfigured gr-dev-un No visual change
Group - Dev tab - Configured gr-dev-con No visual change
Group - Op tab - Unconfigured Empty tab group-op
Instance - Dev tab - Unconfigured in-dev-un No visual change
Instance - Dev tab - Configured in-dev-con No visual change
Instance - Op tab - Unconfigured Empty tab in-op

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 #340342 (closed)

Edited by David O'Regan

Merge request reports