Group Security Dashboard project filter dropdown based on standalone vulnerabilities

Problem to solve

With the move to standalone vulnerabilities from findings, some Group Security Dashboard UI elements are still pulling from the old findings and are thus inconsistent with other dashboard components backed by standalone vulnerability data. This can create user confusion when elements on the same screen are inconsistent.

Intended users

  • Delaney (Development Team Lead)
  • Sam (Security Analyst)

Further details

Proposal

Update the project filter dropdown to only pull projects with standalone vulnerabilities on their respective default branches. Projects that still have findings but do not have standalone vulnerabilities will no longer appear.

Permissions and Security

Documentation

Availability & Testing

What does success look like, and how can we measure that?

What is the type of buyer?

Is this a cross-stage feature?

Links / references

Assignee Loading
Time tracking Loading