Project

General

Profile

Actions

Feature #9851

open

Equalize the way how available shared versions are differentiated in target version drop-downs

Added by Mischa The Evil about 12 years ago. Updated 7 months ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
UI
Start date:
Due date:
% Done:

0%

Estimated time:
Resolution:

Description

I'd suggest to equalize the way how available shared versions are differentiated in target version drop-downs since they differ between issues/new and issues/index. See the following screenshots:

issues/new
issues/index

I'm happy with either one as long as long as we're presenting a consistent UI.


Files

tv_issues-index.jpg (9.13 KB) tv_issues-index.jpg Mischa The Evil, 2011-12-21 03:38
tv_issues-new.jpg (6.95 KB) tv_issues-new.jpg Mischa The Evil, 2011-12-21 03:38

Related issues

Related to Redmine - Feature #9850: Differentiate shared versions in version-format custom field drop-downs by prepending its project nameClosed

Actions
Related to Redmine - Feature #15902: Custom Field - Version - Combo list to be grouped by projects..New

Actions
Related to Redmine - Defect #28865: Group items by project in version type custom fieldsNew

Actions
Has duplicate Redmine - Feature #14449: Versions custom field format Closed

Actions
Actions #1

Updated by Mischa The Evil about 12 years ago

  • Subject changed from Equalize the way how available shared versions are differenciated in target version drop-downs to Equalize the way how available shared versions are differentiated in target version drop-downs
  • Description updated (diff)

Fixing ugly typo.

Actions #2

Updated by Etienne Massip almost 12 years ago

  • Target version set to Candidate for next minor release
Actions #3

Updated by Mischa The Evil over 10 years ago

Actions #4

Updated by Mischa The Evil over 10 years ago

  • Description updated (diff)
Fixed description:
  • Placed screenshots in table to seperate them better, and reordered them;
  • Changed "constant UI" to "consistent UI".
Actions #5

Updated by Toshi MARUYAMA over 8 years ago

  • Related to Feature #19965: values of custom fileds of version type should be prefixed with or grouped by project name added
Actions #6

Updated by Alexis Parent over 8 years ago

+1

Actions #7

Updated by Christophe Portier about 8 years ago

+1

Actions #8

Updated by Mischa The Evil about 7 years ago

  • Related to deleted (Feature #19965: values of custom fileds of version type should be prefixed with or grouped by project name)
Actions #9

Updated by Mischa The Evil about 7 years ago

  • Related to Feature #15902: Custom Field - Version - Combo list to be grouped by projects.. added
Actions #10

Updated by Edgars Batna about 6 years ago

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.

Actions #11

Updated by Greg Burri almost 6 years ago

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.

Actions #12

Updated by flabb17 _ over 4 years ago

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

Actions #13

Updated by Bernhard Rohloff over 4 years ago

  • Related to Defect #28865: Group items by project in version type custom fields added
Actions #14

Updated by Stephane Poss 7 months ago

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

And in lib/redmine/field_format.rb, find the class VersionFormat, and change the possible_values_options to
      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.

Actions

Also available in: Atom PDF