-
-
Notifications
You must be signed in to change notification settings - Fork 158
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for summarized and scheduled notifications #903
Open
MM-msr
wants to merge
12
commits into
DependencyTrack:feature-322-scheduled-notifications
Choose a base branch
from
MM-msr:master
base: feature-322-scheduled-notifications
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Support for summarized and scheduled notifications #903
MM-msr
wants to merge
12
commits into
DependencyTrack:feature-322-scheduled-notifications
from
MM-msr:master
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
MM-msr
changed the base branch from
master
to
feature-322-scheduled-notifications
June 17, 2024 06:15
3 tasks
Signed-off-by: Max Schiller <[email protected]>
Signed-off-by: Max Schiller <[email protected]> Signed-off-by: Marlon Gäthje <[email protected]>
…e view, displays scheduled state in table, removed unnecessary parts from previous commits Signed-off-by: Max Schiller <[email protected]> Signed-off-by: Marlon Gäthje <[email protected]>
…ne of classic alerts) Signed-off-by: Max Schiller <[email protected]>
… API communication Signed-off-by: Max Schiller <[email protected]>
Signed-off-by: Max Schiller <[email protected]> Signed-off-by: Marlon Gäthje <[email protected]>
Signed-off-by: Max Schiller <[email protected]>
Signed-off-by: Max Schiller <[email protected]>
…onding popup message Signed-off-by: Max Schiller <[email protected]> Signed-off-by: Marlon Gäthje <[email protected]>
Signed-off-by: Max Schiller <[email protected]> Signed-off-by: Marlon Gäthje <[email protected]>
Signed-off-by: Max Schiller <[email protected]> Signed-off-by: Marlon Gäthje <[email protected]>
Signed-off-by: Max Schiller <[email protected]> Signed-off-by: Marlon Gäthje <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Currently, Dependency-Track Alerts send a single notification for every single event happening that an alert is subscribed to (e.g. NEW_VULNERABILITY). This can lead to a lot of emails for users and creates the risk of overlooking important notifications.
To improve the user experience of the Alerts, scheduled notifications are implemented in Dependency-Track to send summarized notifications of new events between the last and current scheduled notification. The schedule is defined as cron expression.
Scheduled notification management is available via API in the Backend Pull Request DependencyTrack/dependency-track#3925 and Frontend under Administration -> Notifications -> Scheduled Alerts.
Addressed Issue
DependencyTrack/dependency-track#322
Additional Details
For screenshots, see backend PR: DependencyTrack/dependency-track#3925
Checklist