0005659: Updating an issue causes version to be deleted if version is not marked released

ID	Project	Category	View Status	Date Submitted	Last Update
0005659	mantisbt	bugtracker	public	2005-05-26 13:00	2012-11-01 07:45

Reporter	gtomlin	Assigned To	dregad
Priority	normal	Severity	major	Reproducibility	always
Status	closed	Resolution	no change required
Product Version	1.0.0a2

Summary	0005659: Updating an issue causes version to be deleted if version is not marked released
Description	When updating some other field in an issue, the version field is cleared even though the user makes no change to that field.
Additional Information	This issue came up when working with historical issues we imported from elsewhere. The versions that are no longer supported are not marked as released so that new issues cannot be reported against them. However, it is still valuable to us to know what past version fixed an issue.
Tags	No tags attached.

gtomlin 2005-05-26 14:00 reporter ~0010252	I should note that my scenario involving historical issues is not the only way to be affected by this problem. Updating any issue that has a version that is not marked released at the time the issue is updated will suffer the same problem.

thraxisp 2005-05-26 14:03 reporter ~0010253	The dropdown field for found in version only has released versions. The dropdown will silently default to the first item in the list. It looks like we may need a third category for versions (obsolete).

gtomlin 2005-05-26 14:13 reporter ~0010254 Last edited: 2005-05-26 14:16	We need at least that. Maybe we need an enumeration for version status and a way of configuring which version status value(s) should be allowed in an issue. I can see the need for (at least) development, alpha, beta, released, obsolete. Also see 0004904. Even then, there would be a problem with the existing data being removed from the issue if the version becomes "unacceptable" between the time the issue is reported and the time of some update to the issue.

dregad 2012-10-18 10:04 developer ~0033266	This was fixed in 1.2.9 (see 0013096)