nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

What is sort by Fix Version on atlassian.net sorting with?

David Rayna (PXHG46)

If I use a search via https://COMPANY.atlassian.net/issues/?jql= ..., sorting by Fix Versions shows haphazzard results.

If there a fix/workaround to getting alphabetical or numerical sorting by Fix Versions?

more info: ORDER BY fixVersion ASC

Lists out of order like 2.00 2.00 2.01 2.01 1.74 1.74 1.75

This on cloud.

It might be order the versions were added to Jira, not the values.

Accepted answers

Ryan Fish

@David Rayna (PXHG46)
Not sure what your url is pointing to, but fix version field is not enabled.
normally you can order alphabetically ascending or descending.

"fixVersion is not EMPTY ORDER BY fixVersion ASC"
"fixVersion is not EMPTY ORDER BY fixVersion DESC"

All comments

Ryan Fish

@David Rayna (PXHG46)
Not sure what your url is pointing to, but fix version field is not enabled.
normally you can order alphabetically ascending or descending.

"fixVersion is not EMPTY ORDER BY fixVersion ASC"
"fixVersion is not EMPTY ORDER BY fixVersion DESC"

David Rayna (PXHG46)

I use fixVersion ASC but the results are out of order.

Ryan Fish

@David Rayna (PXHG46)

The sort order is alphabetical but...
Check release names for consistency and order also. That can cause your query sort to be askew.

https://confluence.atlassian.com/jirakb/sort-fix-version-s-into-a-correct-order-on-the-issue-search-result-950290183.html

David Rayna (PXHG46)

That was the problem. The order is the order you specify on that other page. Nothing to do with content at all. How would one ever know.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud