New and Improved 3.13 Beta. Highlights: Shareable filters and dashboards and lots of other goodies. Any feedback can be raised as JIRA issues in the JIRA project.
Issue Details (XML | Word | Printable)

Key: JRA-8558
Type: Improvement Improvement
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: Mark Chaimungkalanont [Atlassian]
Reporter: Miro Lehky
Votes: 1
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
JIRA

Custom Version Field Lists Archived Versions

Created: 17/Nov/05 04:39 PM   Updated: 22/Jan/06 10:27 PM
Component/s: None
Affects Version/s: 3.4.1
Fix Version/s: 3.5

Time Tracking:
Not Specified

Issue Links:
Reference
 

Participants: Dylan Etkin [Atlassian], Erik S, Mark Chaimungkalanont [Atlassian] and Miro Lehky
Since last comment: 2 years, 31 weeks, 2 days ago
Resolution Date: 22/Jan/06 10:27 PM
Labels:


 Description  « Hide
Custom fields using the Version Picker type, list ALL versions. It would seem that when a version is archived that version number should be removed from this custom fields dropp down.

 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Miro Lehky added a comment - 18/Nov/05 06:23 AM
Thanks Mark. I was also wondering if this was as intended or not.

Dylan Etkin [Atlassian] added a comment - 22/Nov/05 06:33 PM
Hi Miro,
I am rescheduling this issue for 3.5. To do this properly we need to make some fairly large changes. The real problem comes in when you have a version selected on a version custom field, then you archive the version, then you edit the issue. If we do not display the archived versions in the options then you will loose the custom fields value on issue update (it will probably default to None). This is not the behavior that we want. Instead we would like the field to act like the fix for and affects version fields, they show any archived versions as text on edit which is not unselectable. If we are going to go this far we should probably just go all the way and turn this into a multi-select custom field while we are at it. So that we won't compromise the stability of the 3.4 releases I am moving this to 3.5. Sorry for any inconvenience.
Dylan

Miro Lehky added a comment - 23/Nov/05 08:32 AM
Thanks Dlyan, that sounds like a reasonable approach. I've also linked this issued to JRA-7263 which I had entered sometime ago. That one sounds like the approach your taking.

Miro


Erik S added a comment - 19/Jan/06 10:06 AM
It would be nice to have the option of multi-select or single select.

Mark Chaimungkalanont [Atlassian] added a comment - 22/Jan/06 10:27 PM
In 3.5, there are now two Version custom field types. A "Single Version Picker" which is a single select of non-archived versions and a "Version Picker" which works pretty much like the Fix For / Affects Version fields