fix(jira): correctly handle issues with null resolution (Fixes #4295) #4370
+60
−1
Conversation
This file contains hidden or 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
…heus#4295) Signed-off-by: hyunuk <nnhope@hotmail.com>
surinkim
force-pushed
the
fix/jira-resolution-null-4295
branch
from
cff001d to
eb81053
Compare
|
Could you please share the Jira integration and Alertmanager configuration? |
|
Here is the Jira integration and Alertmanager configuration I used for testing: Jira Environment
Alertmanager Configuration
|
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.
This pull request fixes a bug where Alertmanager would create a duplicate Jira issue if the existing issue's resolution field was
null(for example, when the issue was still "To Do" or "In Progress").Previously, the search query only checked for
resolution != "Won't Do", so issues withnullresolution were not properly matched, causing Alertmanager to incorrectly create a new issue.This fix updates the JQL condition to also check
resolution is EMPTY or resolution != "Won't Do", ensuring that open issues are correctly found and reused.Changes
nullresolution.Screenshots
Before
resolution != "Won't Do"onlyAfter
resolution is EMPTY or resolution != "Won't Do"Fixes #4295.