0009119: Assigning an issue and then unnassigning it does not work - MantisBT

ID	Project	Category	View Status	Date Submitted	Last Update

0009119	mantisbt	bugtracker	public	2008-04-30 15:05	2010-01-22 12:31

Reporter	consc198	Assigned To
Priority	normal	Severity	major	Reproducibility	always
Status	new	Resolution	open
Product Version	1.1.1

Summary	0009119: Assigning an issue and then unnassigning it does not work
Description	Assigning an issue and then unnassigning it does not work as expected.
Steps To Reproduce	1) Assign an issue to a user 2) Then assign the issue to nobody The issue still stays assigned to nobody, this is wrong the issue should update its status to new.
Tags	No tags attached.

cor3huis 2010-01-22 11:50 reporter ~0024227	I disagree, IMHO this behavior is correct WHY: One can still have a defect with status e.g. "confirmed", but no one to solve it (yet). Unsigned or not the defect still is the same defect after all.

consc198 2010-01-22 12:31 reporter ~0024228	My problem is that let say i assign an issue to a user then for some reason we have to unasign the issue. My opinion is that its wrong for the Status to still remain as Assigned since its actually not assigned, in this case the Status should change back to New or back to where it was before the issue was assigned. I totally agree that a issue can have a status such as confirmed but no assignee, i personally do this a lot of times.