+100. This is a very critical functionality.

Version name (automated) sorting has been an issue with debates and still there seems no universally accepted way. See related issues: #11153 vs. #12814. What is otherwise not reported but becomes even more mess when there are multiple projects sharing their versions across tree/hierarchy and none has a date for it!

Other related issues are: #6881, #7269, #8080

The trouble is, there won't ever be a one-fit-solution-for-all. I think best situation can be if the versions are allowed to be explicitly manually ordered on the versions page.

It doesn't take a genius to make it -but might ease everyone's problems.

+100 please implement this.
--------------------------------------------------------------------------------
+1 from me, too.
We use Versions as "Milestones" with descriptive texts, hence an alphabetical order is not useful to us.
We use redmine to plan our projects, too, and there are no due dates while planning.
This means that versions are in a totally useless order while planning a project, which is a real burden to the planner and makes it difficult to talk about a project in the planning phase based on the roadmap.
--------------------------------------------------------------------------------
+1 too
joining my previous speakers
--------------------------------------------------------------------------------
+1

I think most people want least version in top of the list, like
https://github.com/redmine/redmine/releases
or
http://jmeter-plugins.org/downloads/all/

If I made the PR, will you accept it?
--------------------------------------------------------------------------------
+1
Ideally this should be configurable, but by default the order should by according to the displayed text. I can get what I want by hacking @app/models/version.rb@ to
<pre><code class="ruby">
# Versions are sorted by name
# then by effective date (nulls lose) and then id
def <=>(version)
if name == version.name
if self.effective_date
if version.effective_date
self.effective_date == version.effective_date ? id <=> version.id : self.effective_date <=> version.effective_date
else
1
end
else
-1
end
else
name <=> version.name
end
end
</code></pre>
--------------------------------------------------------------------------------
+1
--------------------------------------------------------------------------------
Will this ever get accepted into redmine? I'm really missing it :(

--------------------------------------------------------------------------------
10 years later, I still need this feature desperately.
--------------------------------------------------------------------------------
I finally solved the roadmap versions sorting issue, see the screenshot, assume we always create bigger version each time.

!{width:25%}version-order.png!

The changed code of: app/models/version.rb
<pre><code class="ruby">
def <=>(version)
if self.effective_date
if version.effective_date
# both have dates
if self.effective_date == version.effective_date
# 1. (v0.1) to (v0.2)
id <=> version.id
else
# 2. (early) to (later)
self.effective_date <=> version.effective_date
end
else
# 3. (date) to (no date)
-1
end
else
if version.effective_date
# 4. (date) to (no date)
1
else
# 5. both no dates, order by id descent
version.id <=> id
end
end
end
</code></pre>
--------------------------------------------------------------------------------

relates,New,6881,Version numbering sort
duplicates,Reopened,12814,Ability to specify target version sort order
duplicates,Closed,8080,Option for alphabetical only sorting of versions (date ignored)
duplicates,Closed,13681,Option to choose sorting versions in roadmap