-
-
Notifications
You must be signed in to change notification settings - Fork 526
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
Alert Rules not working for all projects because of NULL values in PROJECT.ACTIVE #3296
Comments
Additional information: |
After reviewing the code I wonder if this might be related to #3244 as this would be the only condition I could see as a reason for different handling of same projects. Will check once I have DB access edit: Yes this seems to be the issue. Those projects have a NULL value in active field in DB: @nscuro might be a good idea to set all NULL values in "active" to "TRUE" in next version via db upgrade? |
@rkg-mm Doing this change directly in the DB should work, and a restart should not be required.
Yes, but also the notification router code should be able to correctly handle |
… `null` Fixes DependencyTrack#3296 Signed-off-by: nscuro <nscuro@protonmail.com>
… `null` Fixes DependencyTrack#3296 Signed-off-by: nscuro <nscuro@protonmail.com>
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Current Behavior
I have at least 1 project team not getting emails for their projects, despite an alert rule being configured. I added myself as "Destination" additionally to the recipient team to test it and can confirm it. However, the behaviour is strange:
I have a parent-child project relationship like this:
The alert rule is configured on the top level "Project X", with " Include active children of projects " enabled.
The SBOMs are uploaded to the Microservice Projects on 3rd level.
This was seen in 4.9.1, but still the same in 4.10. The new logging feature confirms the behavior.
Steps to Reproduce
Steps might not be exact because there is a strange difference between older projects and a new project I created to test it. However, this is what I see:
There is no visible difference between the "old" projects and the "new" project, and I am unsure when the old ones were created.
Expected Behavior
There should be no difference between the old and new microservice projects. However, only notifications for the new project are sent, even though they are covered by the same notification rule.
Dependency-Track Version
4.10.0
Dependency-Track Distribution
Container Image
Database Server
Microsoft SQL Server
Database Server Version
No response
Browser
Google Chrome
Checklist
The text was updated successfully, but these errors were encountered: