-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Low
-
None
-
Affects Version/s: 8.20.11, 9.5.0, 9.7.1
-
Component/s: Issue - Fields
-
None
-
8.2
-
2
-
Severity 3 - Minor
Issue Summary
Advanced JQL search is broken for Ampersand (&) and other special character while linking an Issue
This is reproducible on Data Center: Yes
Steps to Reproduce
- Create a custom field having values with Ampersand (&) or plus sign (+)
Ex:
Testing Field = "Dealing & Execution" - Add this custom field to the New/existing issue.
- Now link this issue through Advanced Search
- While searching for the issue to link it under issue —> more --> Link --> Search For An Issue --> Advanced search Provide below JQL Query
Testing Field = "Dealing & Execution" - It is throwing “Invalid JQL query.” Error

- The same Advance JQL query with Ampersand (&) special character works fine in Normal Issue Search Screen.

Expected Results
Advance JQL Query with Ampersand (&) special character should list the issue while searching it under the issue link Page.
Actual Results
Advance JQL Query with Ampersand (&) special character shows an “Invalid JQL query” Error while searching the issue under the issue link Page.

Workaround
- If we use the Unicode value of ampersand, it works fine.
- Ex: Testing Field = "Dealing \u0026 Execution"

- Ex: Testing Field = "Dealing \u0026 Execution"
Notes
It also affects searching for Project. In this situation, search using project key instead of the project name.