-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
7.6.4, 8.3.0, 7.13.5
-
None
-
7.06
-
6
-
Severity 3 - Minor
-
1
-
Issue Summary
The sorting is not accurate after the 51st character for text fields.
Steps to Reproduce
- Create a custom field of type Text Field (Single Line) (e.g. "Text Field CF")
- Create multiple issues and a sortable value for the custom field. The field value must be above 52 characters.
For a quick way, use this to generate 99 issuesfor i in {01..99}; do curl -u <username>:<password> -X POST -H "Content-Type: application/json" http://localhost:8080/rest/api/2/issue/ \ --data '{"fields": {"project":{"key": "<pkey>"},"summary": "Issue number '$i'","description": "test","issuetype": {"name": "<Type>"},"customfield_<id>" : "abc123abc123abc123abc123abc123abc123abc123abc123abc-1'$i'"}}'\ ; done
- Search and sort by that field in the issue navigator. E.g.:
"Text Field CF" is not EMPTY ORDER BY "Text Field CF" DESC
Expected Results
Issues would be correctly sorted independently of the number of characters in the field.
Actual Results
Jira only sorts up to the 51st character:
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available
- is related to
-
JRASERVER-69833 'ORDER BY' in JQL on text Fields sorts by ASCII values causing upper and lowercase to be separated
- Gathering Impact
- mentioned in
-
Page Loading...