You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The defect may already be reported! Please search for the defect before creating one.
Current Behavior:
The Audit process for Vulnerabilities is a bit shaky:
The "Details" cannot be set to "". If you try the change is ignored.
Setting/Unsetting Suppress is not reflected in the listing until you click the "Show suppressed Findings" on and off (at least for as long as my patience permits)
Setting "Analysis" to "Not Set" is shown as "Not Set" in the listing whereas items that were never touched show as "-".
Steps to Reproduce:
Try to process a Vulnerability
Expected Behavior:
Updates should be saved in the DB.
UI should reflect the updates
It should be possible to clean Text fields completely
It should be possible to set an audit record back to its original state (possibly less the Audit trail)
Environment:
Dependency-Track Version: 4.5
Distribution: [ Docker ]
BOM Format & Version: N/A
Database Server: [ PostgreSQL ]
Browser: Chrome
Additional Details:
(e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, gitter, etc)
The text was updated successfully, but these errors were encountered:
The defect may already be reported! Please search for the defect before creating one.
Current Behavior:
The Audit process for Vulnerabilities is a bit shaky:
Steps to Reproduce:
Try to process a Vulnerability
Expected Behavior:
Updates should be saved in the DB.
UI should reflect the updates
It should be possible to clean Text fields completely
It should be possible to set an audit record back to its original state (possibly less the Audit trail)
Environment:
Additional Details:
(e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, gitter, etc)
The text was updated successfully, but these errors were encountered: