fix(jira): correctly handle issues with null resolution (Fixes #4295)

[surinkim]

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 with null resolution 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

• Modified the Jira JQL query condition to correctly handle issues with null resolution.
• Added corresponding unit tests to verify this behavior.

Screenshots

Before

• Search JQL: resolution != "Won't Do" only
• Behavior: create new issue even if there is an open issue

After

• Search JQL: resolution is EMPTY or resolution != "Won't Do"
• Behavior: update existing issue properly without creating a duplicate

---

Fixes #4295.

[cicadadevops]

Could you please share the Jira integration and Alertmanager configuration?

[surinkim]

Here is the Jira integration and Alertmanager configuration I used for testing:

---

Jira Environment

• Instance: https://surinkim10.atlassian.net
• Note: This is a temporary trial Jira Cloud project created for testing purposes.
  (External access is restricted.)

---

Alertmanager Configuration

• Configuration details are shared here:
  👉 Alertmanager Jira Test Configuration (Gist)

[cicadadevops]

Has anyone tried integrating Alertmanager with Jira Data Center?
I’m using Jira Data Center version 10.3.6, but unfortunately, I haven’t been able to get it to work correctly.
Sometimes it fails to reopen existing tickets, and sometimes it doesn’t create new ones at all.