|
[
Permlink
| « Hide
]
Miro Lehky added a comment - 18/Nov/05 06:23 AM
Thanks Mark. I was also wondering if this was as intended or not.
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 Thanks Dlyan, that sounds like a reasonable approach. I've also linked this issued to
Miro 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
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||