Add filters to the Dependency List page

The following page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.

Release notes

Problem to solve

Lots of data is present on this page - too much - users want to hone in

what filters should be available?

Proposal

1. A Type filter will be added to allow users to select either System Dependencies or Application Dependencies
2. A Packager filter will be added to allow users to filter by the package manager
3. A Source filter will be added to allow users to filter by the source column (this is especially useful for customers with multiple images in a single project if they need to filter their system dependencies by image)
4. A License filter will be added to allow users to filter by the license column
5. from what scanner DS vs CS [ like Trivy, or gemnasium-maven etc)
6. introduced vs upstream (need that data on backend first to allow for this)
7. development deps vs not (need that data on backend first to allow for this)
8. filter by direct/transient(indirect) dependency

Implementation Plan

frontend

backend

Consider these follow up ~"technical debt" issues

1. #217734 (closed)
2. #11988 (closed)

Availability & Testing

This section needs to be retained and filled in during the workflow planning breakdown phase of this feature proposal, if not earlier.

What risks does this change pose to our availability? How might it affect the quality of the product? What additional test coverage or changes to tests will be needed? Will it require cross-browser testing?

Please list the test areas (unit, integration and end-to-end) that needs to be added or updated to ensure that this feature will work as intended. Please use the list below as guidance.

• Unit test changes
• Integration test changes
• End-to-end test change

See the test engineering planning process and reach out to your counterpart Software Engineer in Test for assistance: https://about.gitlab.com/handbook/engineering/quality/test-engineering/#test-planning

Is this a cross-stage feature?

Communicate if this change will affect multiple Stage Groups or product areas. We recommend always start with the assumption that a feature request will have an impact into another Group. Loop in the most relevant PM and Product Designer from that Group to provide strategic support to help align the Group's broader plan and vision, as well as to avoid UX and technical debt. https://about.gitlab.com/handbook/product/#cross-stage-features -->