0014111: Cannot set Target Version to a version that is released

Notes
(0031560) dregad (developer) 2012-03-29 15:46	You are correct, 0011706 introduced a regression as the case you describe was not taken into consideration by the change. I think the correct way to handle this would be as suggested by rombert, to have a config option setting a threshold for the access level authorized to assign issues to a released version. In the meanwhile, if this is blocking for you I recommend to revert commit 3af57d28.

(0031563) kian (reporter) 2012-03-29 15:59	Thanks for the quick update. The configuration option sounds good - that would work for us. I've reverted in the meantime :)

(0031581) dregad (developer) 2012-03-30 18:43	The commit 3af57d28 will be "officially" reverted in the next release, until a better solution can be designed and implemented.

(0031587) dregad (developer) 2012-04-02 04:06	Newly released Version 1.2.10 reverts to the pre-1.2.9 behavior.

Related Changesets
MantisBT: master-1.2.x daf3c834 Timestamp: 2012-03-30 15:35:14 Author: dregad [ Details ] [ Diff ]	Revert "Prevent selection of released version as target" This reverts commit 3af57d289e46cf467bc30c8a094ce54af06eaf43. The way this feature was implemented in release 1.2.9 introduced regressions for several users. Affects 0011706
	mod - bug_actiongroup_page.php	[ Diff ] [ File ]
	mod - bug_report_page.php	[ Diff ] [ File ]
	mod - bug_update_advanced_page.php	[ Diff ] [ File ]