0013938: Error when editing issue having version not existing in current project - MantisBT - Signup temporarily disabled due to spam

ID	Project	Category	View Status	Date Submitted	Last Update

0013938	mantisbt	bugtracker	public	2012-02-21 19:31	2014-09-23 18:05

Reporter	dregad	Assigned To	dregad
Priority	normal	Severity	minor	Reproducibility	always
Status	closed	Resolution	fixed
Product Version	1.2.9
Target Version	1.2.9	Fixed in Version	1.2.9

Summary	0013938: Error when editing issue having version not existing in current project
Description	When editing an issue having the Product Version field set to a version number which is not defined in the issue's current project (which can happen when the issue has been moved from another project, or a version has been deleted from the current project), APPLICATION ERROR 1601 - Version "" not found occurs
Additional Information	This was reported by atrol in 0013935:0031282
Tags	No tags attached.

dregad 2012-02-21 19:39 developer ~0031287	This regression issue was introduced by the fix for 0013096. The error occurs because the version field in the bug table is not cleared when the issue is moved, so when Mantis is building the version selection list to edit the bug, it tries to add the version defined in it to the list, which triggers the error since that version does not exist in the current project. An additional check for the validity of the matching version ID is required, as suggested by atrol in 0013935:0031283.

grangeway 2013-04-05 17:57 reporter ~0036368	Marking as 'acknowledged' not resolved/closed to track that change gets ported to master-2.0.x branch

MantisBT: master a939b3e7 2012-02-21 11:39 dregad Details Diff	Avoid error when editing bug with invalid version When editing an issue having the Product Version field set to a version number which is not defined in the issue's current project (which can happen when the issue has been moved from another project, or a version has been deleted from the current project), APPLICATION ERROR 1601 - Version "" not found occurs. The error occurs because the version field in the bug table is not cleared when the issue is moved, so when Mantis is building the version selection list to edit the bug, it tries to add the version defined in it to the list, which triggers the error since that version does not exist in the current project. Regression caused by commit 0ffb20f8807fc600750690e201ebf5fb325e7bfc Fixes 0013938		Affected Issues 0013938
	mod - core/print_api.php		Diff File
MantisBT: master-1.2.x 081ca287 2012-02-21 11:39 dregad Details Diff	Avoid error when editing bug with invalid version When editing an issue having the Product Version field set to a version number which is not defined in the issue's current project (which can happen when the issue has been moved from another project, or a version has been deleted from the current project), APPLICATION ERROR 1601 - Version "" not found occurs. The error occurs because the version field in the bug table is not cleared when the issue is moved, so when Mantis is building the version selection list to edit the bug, it tries to add the version defined in it to the list, which triggers the error since that version does not exist in the current project. Regression caused by commit a68398245663d25229800638b6965ffe6e7ab0d3 Fixes 0013938		Affected Issues 0013938
	mod - core/print_api.php		Diff File