Fix Version Sorting Issue: Descending Order Not Working as Expected

[juan.baliarda]

I have a filter that retrieves multiple tickets with associated Fix Versions. The naming convention we use for Fix Versions is YY.MM-Month. However, I’m facing an issue when sorting the table by Fix Versions in descending order.

The expected sorting logic should be as follows:
25.02, 25.01, 24.12, 24.11, and so on.

But the actual sorting appears inconsistent, resulting in something like:
25.02, 24.12, 25.02, 25.01.

It doesn't seem to follow any recognizable pattern. Since the Fix Versions field is a default Jira field and not a custom one, I cannot adjust its configuration.

[Trudy Claspill]

Hello @juan.baliarda 

I found this post from 2020 saying that the sort order is based on the order the versions appear in on the Releases page.

https://community.atlassian.com/t5/Jira-questions/What-is-sort-by-Fix-Version-on-atlassian-net-sorting-with/qaq-p/1320478

And there is this change request:

https://jira.atlassian.com/browse/JRACLOUD-42225

[juan.baliarda]

Hi, thanks for the quick response! I went through what you shared and noticed something. The releases I want to sort are from different projects. While the releases are sorted correctly within each project, when I try to sort all the releases across projects, Jira groups them by project first. This grouping is what’s making the table look strange. The sorting technically works, but I’m not sure why it’s grouping by project.