DependencyTrack / DependencyTrack/dependency-track
Policy Violations indicators are showing"0" instead of real number of Violations
- Dominant language
- Java
- Stars
- 4.2k
- Forks
- 811
- Avg merge
- 8h 39m
- Merged PRs (30d)
- 237
Description
### Current Behavior
Once Policy Violations are found, in the Projects view the number of Violations are correctly indivcated.
But in the Project itself view the indicators are "0" even thogh that the number should be other then "0".


### Steps to Reproduce
1. Compare the Policy Violations findings between the Projects view to a Project view.
### Expected Behavior
Same results should be shown on both views, Projects and individual Project.
### Dependency-Track Version
4.12.0
### Dependency-Track Distribution
Executable WAR
### Database Server
Microsoft SQL Server
### Database Server Version
MSSQL Enterprise 2022
### Browser
Microsoft Edge
### Checklist
- [x] I have read and understand the [contributing guidelines](https://github.com/DependencyTrack/dependency-track/blob/master/CONTRIBUTING.md#filing-issues)
- [x] I have checked the [existing issues](https://github.com/DependencyTrack/dependency-track/issues) for whether this defect was already reported
Contributor guide
Research direction
Reproduce the discrepancy by comparing the Policy Violations indicators in the Projects view with the individual Project view, using the reported Dependency-Track 4.12.0 setup as needed. Trace why the individual Project view displays zero while the Projects view shows findings; done means both views show the same nonzero violation count.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, sql
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100