-
Type:
Bug
-
Resolution: Duplicate
-
Priority:
Medium
-
None
-
1
-
Minor
Issue Summary
When a field has an ampersand '&' the API used to fetch field suggestions fails to return any results as it does not encode the '&' properly.
Example field name: "Multi choice select&list"
URL constructed for suggestions: https://site.atlassian.net/rest/api/latest/jql/autocompletedata/suggestions?fieldName=Multi%20choice%20select&list[Select%20List%20(multiple%20choices)]&fieldValue=a
Note the '&' after "select" and before "list" in the above URL is not encoded, thus is interpreted as a parameter separator, instead of the actual character.
Steps to Reproduce
- Create a custom field with a '&' character
- Use Advanced JQL search and notice suggestions for custom field options fail
Expected Results
Ampersands should be encoded properly so proper field value suggestions are returned
Actual Results
Ampersands are not properly encoded, return object will always be an empty array
Workaround
Remove ampersands from custom field names
- duplicates
-
JRACLOUD-93461 Suggestion for Select List fields don't work when custom field name contains special characters in New Issue Search
-
- Closed
-