Data export functionality in search masks e.g., "Vulnerability Audit"

[BoaThor]

Current Behavior

Use Case:
You want a report of a projects newly attributed vulnerabilities.
You set the filters e.g., date, severity, projects.
You get presented with e.g., 35 tickets high to critical.
You want to have this list for your sprint daily, or daily reporting meeting.

Issue:
There is no easy way of doing exports.
You cannot export the data directly via the WebUI Frontend e.g., a download as "HTML, ADOC, YAML, JSON, CSV" function has not been build into Dependency Track yet.

Workarounds:

• You need to cut and paste the data manually from the HTML file.
  --> You have to convert the HTML-Table to a JSON or CSV on your own.
• You have to write a API data extractor and execute program regularily.
• You can do screenshots.

Proposed Behavior

Desired Solution(s):

1. Either give simple to use API Endpoint e.g., project with newly attributed vulnerabilities - (takes date and severity) - currently a report like this requires chaining and caching multiple requests - making the logic complex for beginners - and on server with multiple big projects the execution is not extremely fast.

2. Put a simple download function - common to most if not all web-frameworks - to the interface.

Workflow:
User sets filter(s).
Data is loaded.
Data is presented.
An active interface element (button, link, menu) is presented to the user next to the result table - if there is more than 0 hits for the filter.
(Optionally: The user selects the desired data format e.g., raw, yaml, json, html, xml, csv, table dump, keyval etc. etc..)
The user operates the interface element.
The user will be prompted by the browser for the download.
The download is completed - the data is stored at the users machine.

Final result:
After people specified the filter and results have been loaded from the DB completly there should be a "link", "download button" or "drop downmenu (with format options)" will be presented to the user, enabling the frontend user to download the filtered data (e.g., vulnerability audit).

Checklist

• I have read and understand the contributing guidelines
• I have checked the existing issues for whether this enhancement was already requested