-
Type:
Suggestion
-
Resolution: Timed out
-
Component/s: Work Item - Search - Backend - JVIS
-
1
Issue Summary
While ordering a JQL by ID, which should order by the unique ID as stated on the documentation, it is actually using the Issue Key to order the results.
Steps to Reproduce
- Use the ORDER BY ID on the Advanced Issue Search or in API calls
- Check the results
Expected Results
Issues are ordered by their unique Jira ID as mentioned on the documentation
Actual Results
Issues are ordered by the Issue Key instead of the expected unique ID
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available
- blocks
-
JST-779387 Loading...
-
KNOW-22037 Loading...