Project

General

Profile

Actions
Copy link

Feature #19965

closed

values of custom fileds of version type should be prefixed with or grouped by project name

Added by Frederic Cand almost 9 years ago. Updated over 7 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Custom fields
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Resolution:

Description

Steps to reproduce
  • create projects hierarchy
  • create versions shared with project tree
  • create a custom field attached to issues, type version, attached to a tracker of one of the above project
  • create a new issue
Actual result
  • whereas shared versions are grouped by projects in "target version" field, versions in custom field are flat (if some versions are the same in different projects, they are displayed indistinctly)
Expected result
  • shared versions in custom field should be either prefixed with project name, or grouped by project name; just like for "target version"

Related issues

Related to Redmine - Feature #19966: Related issues displayed on "issues" page should be prefixed by project nameNew

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

Actions
Actions
Copy link

Also available in: Atom PDF