Feature #9851
Equalize the way how available shared versions are differentiated in target version drop-downs
| Status: | New | Start date: | ||
|---|---|---|---|---|
| Priority: | Normal | Due 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.
Related issues
History
#1
Updated by Mischa The Evil over 5 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 about 5 years ago
- Target version set to Candidate for next minor release
#3
Updated by Mischa The Evil almost 4 years ago
- Duplicated by Feature #14449: Versions custom field format added
#4
Updated by Mischa The Evil almost 4 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 almost 2 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 almost 2 years ago
+1
#7
Updated by Christophe Portier over 1 year ago
+1
#8
Updated by Mischa The Evil 5 months 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 4 months ago
- Related to Feature #15902: Custom Field - Version - Combo list to be grouped by projects.. added