-
Bug
-
Resolution: Fixed
-
Medium
-
8.9.3, 8.5.12, 8.9.4
-
1
-
Severity 3 - Minor
-
Issue Summary
Confluence uses the incorrect JQL to search Jira issues on certain projects via Insert Jira Issue/Filter. While the issue happens, Confluence uses "jql=summary...OR+description..." instead of using "jql=key" to search for the issue, which causes the search results not to be found.
This is reproducible on Data Center: (yes)
Steps to Reproduce
- Install Confluence and Jira.
- Connect Confluence to Jira.
- On Jira,
- Create two projects following the Jira project key format: one named ABCD, and another named R2D2 for the project name and project key.
- Create at least one ticket on both projects, so there will be two issues, which are ABCD-1 and R2D2-1 to be searched.
- On Confluence,
- Create a page > "+" (Insert more content) > Jira Issue/Filter
- Used ABCD-1 to search, the search result is successful as screenshot below.
- Used R2D2-1 to search, the search result shows No search results found as screenshot below.
- Check the HAR file to compare these two cases:
- Confluence use JQL below to search ABCD-1:
jql=key+%3D+ABCD-1
- Confluence use JQL below to search R2D2-1:
jql=summary+%7E+%22R2D2-1%22+OR+description+%7E+%22R2D2-1
- Confluence use JQL below to search ABCD-1:
Expected Results
Confluence should use "jql=key" to search every keyword so that the Jira issue key can be searched.
Actual Results
Certain keywords will be treated incorrectly like R2D2-1.
Workaround
For the single issue display, we can paste the URL of the issue directly onto the Confluence page. Confluence will auto-convert the link to a Jira Issues macro as mentioned in the document below:
We can also specify "key=issue_key" while searching the issue key like below:
- mentioned in
-
Page Failed to load
A fix for this issue is available in Confluence Data Center 9.1.0.
Upgrade now or check out the Release Notes to see what other issues are resolved.