DependencyTrack / DependencyTrack/dependency-track
Ability to repeat notifications for Integrations
- Dominant language
- Java
- Stars
- 4.2k
- Forks
- 811
- Avg merge
- 8h 39m
- Merged PRs (30d)
- 237
Description
### Current Behavior
Currently, for integrations such as JIRA if there is a network outage, ability to recover from the errors and recreate the notification/ticket is not possible.
Additionally, if projects were previously scanned and an integration added later there is no way to create unresolved entries from a historical perspective.
Potential duplicate/extension of #2674
### Proposed Behavior
- Include a function/api that would allow to re-notify of issues into an integration.
- Possible editable field for the finding to track if it has been logged already, and a power user the ability to unmark it (similar to "mark as unread" in email programs)
- The Transactional Outbox mentioned in #2674 would complement this too instead of a new field
### 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.