Issue Summary

When searching for a Jira issue key within the Jira Issue Macro (Jira Work Items Macro), Confluence uses different JQL construction logic based on the project key pattern.

• Standard Keys (e.g., TEST-1): The macro correctly identifies this as an issue key and generates a query including key = TEST-1.

• Alphanumeric Keys (e.g., TEST1-1): The macro fails to recognize this as a specific issue key. Instead, it treats it as a generic text string and generates a query like text ~ "TEST1-1*" OR summary ~ "TEST1-1*".

Because Jira's text/summary search does not always index the issue key itself, the search returns no results, even though the issue exists.

Steps to Reproduce

1. Create a Jira project with a number in the key (e.g., Name: Project 1, Key: P1).
2. Create a new Jira ticket in that project (e.g., P1-1).
3. In a Confluence page, insert the Jira Issue Macro.
4. In the search bar of the macro, type P1-1.
5. Observe the search results and (optionally) the JQL generated in the browser's Network tab.

Expected Results

The ticket P1-1 should be found and displayed because the macro should include key = P1-1 in the JQL.

Actual Results

The macro returns "We couldn't find anything matching your search". The generated JQL is missing the key = parameter and only performs a text/summary search.

Workaround

1. Switch to the JQL tab within the macro and manually enter key = P1-1.
2. Alternatively, paste the direct URL of the Jira issue onto the Confluence page.