Details
-
Suggestion
-
Resolution: Unresolved
-
None
-
0
-
1
-
Description
NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.
The idea is essentially the same as presented in JRA-846 but for versions instead of components ( http://jira.atlassian.com/browse/JRA-846?focusedCommentId=183746&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-183746 ):
[1] [1.0] [1.0.0] [1.0.1] [1.0.2] [1.1] [1.1.0-Beta-3] [1.1.0-CR-1] [1.1.0] [1.1.1] [2] [2.0] ...
The end result is simply to allow better version-based searching. To me there seems to be numerous ways to accomplish this (pattern recognition, hierarchy with explicit parent selection).
Attachments
Issue Links
- is duplicated by
-
JRASERVER-27781 Improve nested versions
- Closed
- relates to
-
JRACLOUD-23170 Ability for JIRA to understand version hierarchies
- Gathering Interest
- mentioned in
-
Page Loading...