Hello.
This record JRA-28826 was originally a bug and has three related bugs that were closed as duplicates; then Atalssian closed this record on 2015 with the explanation that "the feature didn't get attraction".

I understand your Atlassian's strategy of sorting query results based on the version order; however, I don't agree with dismissing the fact that the manual sorting of the versions page is very inefficient.

The version order affects us with query results, version lists fields, etc, so I asked support to open a another ticket asking Atlassian to provide a more efficient way to organize the version entries in the Project's Version page.

If you are interested in this solution, please vote on this issue:
https://jira.atlassian.com/browse/JRA-61828

Thanks for taking the time to raise this issue.

Due to the large volume of JIRA feature suggestions, we have to prioritise our development efforts. In part, that means concentrating on those issues that resonate the most with our users.

I am writing this note to advise you, that we have decided to close your Suggestion as it has not gained traction on jira.atlassian.com. We believe being upfront and direct with you will assist you in your decision making rather than believing Atlassian will eventually address this issue.

Thank you again for your suggestion and if you have any concerns or question, please don’t hesitate to email me.

Kind Regards,
Kerrod Williams
JIRA Product Management
kerrod.williams at atlassian dot com

I believe the current behaviour (as of 6.3; sorting by order defined in project versions configuration screen where you drag&drop versions to reorder) is the correct one.

Alphabetic order is not what you usually want in software projects - "10.0" would be < than "9.0" if you order alphabetically.

What we might actually want to implement is "ORDER BY fixVersionName" or similar syntax

That is correct. The summary does not match what has been reported. The real issue is in the issue navigator sorting by Fix version column.

Can you clarify why you changed this from a bug to an improvement as well as changed the summary as it does not align with what was reported. Although, it may be helpful to have that as an improvement. The bug is when you are using the issue navigator and include Order By FixVersion ASC, the issues are then ordered by the internal version ID instead of the version name. The user is very confused by this as they would never expect having their issues ordered by an internal ID and it is not apparent to them why the issues are ordered the way they are. Users expect to have the data ordered by the values that they see.

The impact of this is for our summary reports for executives and teams. We use sorting to make it easy to locate the details for the specific fixversion. For our client implementation team, fixversion is the client implementation; thus, we can have 50+ of these going on as active projects. Having them not appear in the correct sort order causes user confusion.