Redmine

+1

This issue also affects me.

Please fix, still an issue in 0.9

Just upgraded to 0.9, and found this problem. Is this scheduled to be fixed ?

Would love to see this fixed as well. Really makes the grouped view (when grouping by Version) impossible to use.

I just want to confirm that I'm still experiencing the same problem. Our most crucial report Groups by Target Version, and the default order is backwards! We have to scroll to the bottom of the report to see our most current Release. Very frustrating.

Redmine 1.0.4.stable.4552 (MySQL)

Still an issue as of 1.1.1. Annoying when using group by target version, and have several pages of issues.

bump.

Group by target version is an issue on our larger projects. Newer target versions, that we add later in the cycle, are sorting to the stop of the group-by list. Thus the current/active release always are pushed down near the bottom.

Sorting by target version should either sort alpha-numeric ascending (so v01.10 would show up before v01.20) or even better would be to make the system sort by release date if target version is the grouping (much like road map & settings/versions).

We too need a fix for this. Or, as it is a feature from now, we need this feature.

+1
This is an important feature, so you can view the full Issue list like a roadmap. Please give it high priority so it can be included soon.

+1
Quite important I think to have a nice view.

+ 1
Annoying when using issues with customer that the highest version comes on top.

+ 1
The nice thing about grouping issues by version is that the unassigned issues form a product backlog. It would be helpful if these groupings could be sorted so that the current sprint/version is first on the list.

+1

In the meantime, I've added the following patch in a new file config/initializers/versions.rb:

require 'app/models/query'

class Query < ActiveRecord::Base
  after_initialize :reset_versions_order

  # Updates the list of available columns to specify ascending as order for versions
  def reset_versions_order
    @@available_columns[10] = QueryColumn.new(:fixed_version, :sortable => ["#{Version.table_name}.effective_date", "#{Version.table_name}.name"], :default_order => 'asc', :groupable => true)
  end
end

But maybe you can think of a better way to update this list of columns (those are my very first lines of code in RoR)?

+1

+1

I tried the patch by Stèphane but it does not work for me... Or at least I don't know how to make it work...

+1

Major efficiency impediment. Anyone have a temporary work around?

I've just updated to Redmine 1.4.1 and indeed my patch did not work any more. Here is a new one:

require 'app/models/query'

class Query < ActiveRecord::Base
  # Updates the list of available columns to specify ascending as order for versions
  def after_initialize
    @@available_columns[10] = QueryColumn.new(:fixed_version, :sortable => ["#{Version.table_name}.effective_date", "#{Version.table_name}.name"], :default_order => 'asc', :groupable => true)
  end
end

Great, thank you! Just unzip it in the plugin directory and restart redmine?

That's it, Rick!

So, just to be clear, this plugin only changes the sort order of the Versions from descending to ascending. It doesn't add the ability to (re)sort the groups in any way.