Feature #9851

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

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

Status:NewStart date:
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:UI
Target version:Candidate for next minor release
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.

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

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

Related issues

Related to Redmine - Feature #9850: Differentiate shared versions in version-format custom fi... Closed
Related to Redmine - Feature #15902: Custom Field - Version - Combo list to be grouped by proj... New
Related to Redmine - Defect #28865: Group items by project in version type custom fields New
Duplicated by Redmine - Feature #14449: Versions custom field format Closed

History

#1 Updated by Mischa The Evil about 8 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.

#2 Updated by Etienne Massip over 7 years ago

  • Target version set to Candidate for next minor release

#3 Updated by Mischa The Evil over 6 years ago

#4 Updated by Mischa The Evil over 6 years ago

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

#5 Updated by Toshi MARUYAMA over 4 years ago

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

#6 Updated by Alexis Parent over 4 years ago

+1

#7 Updated by Christophe Portier about 4 years ago

+1

#8 Updated by Mischa The Evil about 3 years ago

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

#9 Updated by Mischa The Evil almost 3 years ago

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

#10 Updated by Edgars Batna about 2 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.

#11 Updated by Greg Burri over 1 year 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.

#12 Updated by flabb17 _ 7 months ago

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

#13 Updated by Bernhard Rohloff 7 months ago

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

Also available in: Atom PDF