Actions
Feature #19965
closed
values of custom fileds of version type should be prefixed with or grouped by project name
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
- 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)
- shared versions in custom field should be either prefixed with project name, or grouped by project name; just like for "target version"
Related issues
Updated by
Updated by Toshi MARUYAMA over 9 years ago
- Category changed from UI to Custom fields
Updated by Toshi MARUYAMA over 9 years ago
- Related to Feature #19966: Related issues displayed on "issues" page should be prefixed by project name added
Updated by 
Updated by
Updated by Mischa The Evil over 9 years ago
Updated by Toshi MARUYAMA over 9 years ago
- Related to Feature #9850: Differentiate shared versions in version-format custom field drop-downs by prepending its project name added
Updated by Toshi MARUYAMA over 9 years ago
- Related to Feature #9851: Equalize the way how available shared versions are differentiated in target version drop-downs added
Updated by Mischa The Evil almost 8 years ago
- Related to deleted (Feature #9851: Equalize the way how available shared versions are differentiated in target version drop-downs)
Updated by Mischa The Evil almost 8 years ago
- Status changed from New to Closed
Actions