Dropdown sort for fixVersions and affectsVersions

[Goran Dermeta]

Hi guys, 

I was looking in the list of releases we have in one of our project and found out that sorting works a bit wonky.

I have sorted the releases manually in the project release pane, and that translates well for the FixVersions dropdown field on a specific issue.

On the other hand, Affects Versions drop down menu on the same issue has completely unlogical sorting, partly it follows the fixversions, but there are some unreleased releases positioned in a completely unexpected positions in drop down menu.

Start and release date don't play any role as far as i see, nor the number of issues or progress bar.

Does anyone have any idea on how the sort works for those two dropdowns?

[Bill Sheboy]

Hi @Goran Dermeta 

There are several defects and suggestions around the sorting in those fields, with some of them over a decade old, such as this one: https://jira.atlassian.com/browse/JRACLOUD-42225

My understanding of the current behavior (although I have not tested it recently) is to show:

• unreleased versions (which are not archived) in "release order"
  • i.e., bottom to top on the versions page --> inverts to top to bottom in the fields
• released versions (which are not archived)

Kind regards,
Bill

[Goran Dermeta]

Still nobody found a logical explanantion on the field sorting behaviour?