I like to sort issues by key with subtasks directly under the parent.
So I tried the solution proposed here: Sort Issue Navigator by parent-children pairs
After creating the scripted field as suggested, the sorting ("ORDER BY 'Parent Issue Key' ASC, key ASC") only works, if the Parent Issue Key has no Search Template specified. However parent issue key "999" comes after "1000". Using "getNumber()" instead of "getKey" (scripted Field template Number) the same problem occurs. Sorting only works if no search template is specified and 999 comes after 1000.
Is there a good possibility to order subtasks directly under the parent, or is there a mistake in defining the scripted field?
Thanks in advance.
You'll likely need to search by id instead of key. Otherwise it compares them as text as explained here.
You can change:
That should then sort them numerically using the query:
ORDER BY "Parent Issue ID" ASC, id ASC
Your search template will need to be a number field now.
There are a few gotchas when it comes to running JQL searches in scripted fields which is all documented here if you run into inconsistency issues.
Hello, Community! My name is Gosia and I'm a Product Manager on Jira Server and Data Center here at Atlassian. Since 2002 when we launched our public issue tracker, jira.atlass...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs