| Key: |
JRA-5316
|
| Type: |
Improvement
|
| Status: |
Open
|
| Priority: |
Major
|
| Assignee: |
Unassigned
|
| Reporter: |
Keith Brophy
|
| Votes: |
30
|
| Watchers: |
16
|
|
If you were logged in you would be able to see more operations.
|
|
|
With the ability to group versions, certain tasks become simpler - e.g. at present, searching for all issues associated with the JIRA 3.x releases involves searching for 3.x Standard, 3.x Professional, 3.x Enterprise.
With a version 'family', it would be possible to search against the 'Version Family' 3.
|
|
Description
|
With the ability to group versions, certain tasks become simpler - e.g. at present, searching for all issues associated with the JIRA 3.x releases involves searching for 3.x Standard, 3.x Professional, 3.x Enterprise.
With a version 'family', it would be possible to search against the 'Version Family' 3.
|
Show » |
|
Add ability to group versions
Here are my comments:
I would be helpful if you could define multiple releases per version. For Example:
3.0 (Version)
This would enable logging issues against the release (1.0 RC1 etc) rather than the version and still be able to generate release notes for the version which would include all issues logged againts all releases for the version.
This would also be helpful for using JIRA for planning. You could schedule each release and track progress by release. You should be able see overall progress for the version as well.