SLA computation throws exception when a FindingGroup doesn't have a JIRA #8047
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
Maffooch
approved these changes
May 3, 2023
blakeaowens
approved these changes
May 3, 2023
cneill
approved these changes
May 4, 2023
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
We get this error with SLA computation when a FindingGroup doesn't have a JIRA:
[03/May/2023 07:30:00] INFO [dojo.utils:1796] About to process findings for SLA notifications.
[03/May/2023 07:30:03] ERROR [dojo.tasks:157] An unexpected error was thrown calling the SLA code: Finding_Group has no jira_issue.