0005777: Close immediately does not always mark bug as closed

ID	Project	Category	View Status	Date Submitted	Last Update
0005777	mantisbt	bugtracker	public	2005-06-13 12:45	2014-10-14 16:22

Reporter	russ	Assigned To	grangeway
Priority	normal	Severity	minor	Reproducibility	always
Status	closed	Resolution	no change required

Summary	0005777: Close immediately does not always mark bug as closed
Description	Using 1.0.0a3: Have the following statuses: $g_status_enum_string = '10:new,20:feedback,30:acknowledged,40:confirmed,50:assigned,60:fixed,70:stage,80:resolved,90:closed'; Items are considered "resolved" when changed to the fixed status. If I select close immediately when changing the status to fixed, the bug is marked closed as expected. If I select close immediately when changing the status to stage or resolved, the bug is not marked as closed.
Tags	No tags attached.

thraxisp 2005-06-13 14:57 reporter ~0010496	The automated close only works from a change that takes the status from something to exactly "bug_resolved_status_threshold". This should probably be greater than or equal to resolved, and less than closed.

grangeway 2014-10-05 14:13 reporter ~0041394	Functionality described here has changed The config value has been marked as deprecated in 1.3: config_obsolete( 'allow_close_immediately' ); Therefore, would need this tested against latest mantisbt and some feedback on what would be required to be changed in the current git repository to aid this issue.