DependencyTrack / DependencyTrack/dependency-track
Include parentName and isLatest in alert notification limitations for better grouping across project versions
- Dominant language
- Java
- Stars
- 4.2k
- Forks
- 811
- Avg merge
- 8h 39m
- Merged PRs (30d)
- 237
Description
### Current Behavior
Alert notifications in Dependency-Track can currently be limited by:
- A specific project-version combination
- Specific tags
However, there is no support for parentName in the alert notification system.
In my use case, I structure multiple projects so that:
- Each version of a logical application is a separate project (basically the same projectName + a new version number).
- These projects are grouped under the same parentName (the projectName itself, I have some exceptions where the parentName is not the projectName as it contains multiple projects).
- The latest version is marked with the isLatest flag.
This approach allows me to logically manage versioned software. But without parentName in alert notifications, I cannot:
- Correlate issues across different versions
- Limit or prioritize alerts only to the isLatest version
- Aggregate alerts by logical application group
### Proposed Behavior
Include parentName in the alert notification "Limit To" options:
- Allow alert notification scoping by parentNam and isLatest flag, in addition to existing project/version and tags.
This would:
- Enable grouping alerts across versions under the same logical project
- Allow to route alerts more intelligently, e.g., only for latest active versions
- Help focus on what matters operationally
### 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 enhancement was already requested
Contributor guide
Assessment
This issue has not been assessed yet.