Open msymons opened 1 week ago
This one will need a bit more thought since we don't store the modification timestamp on a per-field basis. The only thing with timestamps are comments (i.e. entries in the audit trail). But those are unstructured text, so it's not necessarily easy to programmatically determine what was done.
Current Behavior
The Vulnerability Audit screen is a useful tool that will usually (or hopefully) lead to a lot of additional audit decisions being made. After a while you might have hundreds (or thousands) of audit decisions recorded in Dependency-Track.
Good practice will include reviewing decisions. However, there is no functionality that allows filteringAd by audit timestamps. eg
Proposed Behavior
Add support for filtering by Audit Timestamps.
Note that the audit trail will include multiple timestamps. eg:
The comment timestamp should not "break" filtering for vulnerabilities based on analysis state.
Checklist