Redmine

+1

+1

Make all version fields be presented similarly to the Target Version field (grouped by project name).

Also, take into account that the project name alone does not say much, if the project is in hierarchy with other, similarly named projects. Parent project names should be prepended to the project name.

You can test this and see that version management is impossible in Redmine once there are multiple hierarchy levels and trees.

I just tested this case with the 3.4.4 version of Redmine and it doesn't seem fixed. Custom fields displayed as a list with the Version format aren't prefixed with the project name when issue is edited so you can't distinguish between two versions having the same name but owned by different projects.

+1
Same situation as describe by Gred Burri :
See #28865

As a work around for everyone passing by looking for a 'solution': here is an improvement. In app/models/version.rb, add a to_s_with_project_status method with content

  def to_s_with_project_status
    "#{project} - #{name} - #{status}" 
  end

      def possible_values_options(custom_field, object=nil)
        possible_values_records(custom_field, object).sort.collect do |v|
          [v.to_s_with_project_status, v.id.to_s]
        end
      end

This will prefix the version in the list with the project name and postfix with the status. It's not ideal, but could help.