[#JRA-2345] Ability to specify Current Version

JIRA

Ability to specify Current Version

Created: 16/Sep/03 12:04 PM Updated: 26/May/08 06:18 AM

Component/s:

Web interface

Affects Version/s:

2.4.1

Fix Version/s:

None

Time Tracking:

Not Specified

Participants:	Brian Nguyen, Darren Gibbons, Jon Nichols and Thomas Watson Steen
Since last comment:	141 weeks, 1 day ago
Support reference count:	3
Labels:

Description

« Hide

Our testers are sometimes mis-entering (or not entering at all) the "Affected Versions" on new bug reports.

It would be useful to be able to (optionally) set a "Current Version" in the version setup of the project administration screens. Then, when creating new issues, the "Affected Version" would default to whatever the current version is.

All

Comments

Work Log

Change History

Sort Order:

Ascending order - Click to sort in descending order

[ Permlink | « Hide ]

Thomas Watson Steen - 18/Sep/03 06:59 AM

If this is done, it should be possible for an administrator to determine if he or she wants to use this new functionality. I would not like the idea that JIRA automatically defaults to a version if no one is chosen by the reporter.

This is because that not all users use the same version - but some might still think that they are using the "current" version - even if they are not.

[ Permlink | « Hide ]

Darren Gibbons - 18/Sep/03 12:44 PM

Agreed. The ability to specify the current version should be optional – the project administrator should be able to specify "None".

[ Permlink | « Hide ]

Jon Nichols - 03/Nov/05 11:43 PM

This is important to allow us to create search filters based on the current version. Currently, we have to change all of our filters when we move to a new version, which for us, is every 3 weeks.

[ Permlink | « Hide ]

Brian Nguyen - 04/Nov/05 12:52 AM

Hi Jon,

A possible workaround is to search for 'Unreleased Versions'. In most cases this would relate to the 'Current Version', so you would not need to re-enter any of your search filters.

Thanks,
Brian