Equalize the way how available shared versions are differentiated in target version drop-downs
|Target version:||Candidate for next minor release|
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:
I'm happy with either one as long as long as we're presenting a consistent UI.
#1 Updated by Mischa The Evil over 10 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.
#10 Updated by Edgars Batna over 4 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 almost 4 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.