View Issue Details

IDProjectCategoryView StatusLast Update
0006061mantisbtwebpagepublic2016-04-29 09:05
Reporternuclearspike Assigned Tocproensa  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionfixed 
Product Version1.0.0a3 
Summary0006061: Issues being put back to "Assigned" if assignment changes (to another user) when on different status.
Description

Create an issue, assign it, switch the status to something else (other than "assigned", re-assign to another user. The issue is now back to "Assigned" even though it had moved to another stage. I think that the issue should only change it's status to "Assigned" when changing the assigned user ONLY if no other user had ever been assigned.

Additional Information

We have added a number of other issue status options, including "Estimate Needed", "Estimate Sent" and "Client Approval" when an issue requires a pay-for mod to be done. It comes in, gets triaged and stuck in the "Estimate Needed" assigned to the person who should do the estimation. Once we get approval from the client for the hours, it is reassigned to the developer who will do the work. The problem is that it loses it's status of "Client Approval" which we want to differentiate from "Assigned" in that money is involved and it's a higher visibility issue with that client.

Our usage may be different enough that no one else encounters the problem of it changing the status back to Assigned whenever it is re-assigned. Though I can think of other scenarios in which the automatic status change is also undesired.

TagsNo tags attached.

Relationships

related to 0004469 acknowledged "Reply To Feedback" Button 

Activities

grangeway

grangeway

2014-10-09 17:04

reporter   ~0041499

So question here is whether "assign to" should only change ownership of issue and not status

dregad

dregad

2014-10-10 05:40

developer   ~0041521

I agree with the proposal to not change issue status with the "Assign To" button, except when the assignee is not set.

It's probably worth mentioning that I have a work-in-progress branch for a similar issue related to issues in feedback state always switching back to 'assigned' instead of going back to the previous state the issue was in (see 0004469).

cproensa

cproensa

2016-04-17 14:32

developer   ~0052968

We are resolving this issue as "no change required", because it was reported against an old version of MantisBT which is no longer supported.

We recommend that you upgrade to the latest stable version [1]; if after doing so the problem still exists, do not hesitate to reopen the issue.

[1] http://www.mantisbt.org/download.php

Additionally, at current version 1.3.0-rc1, the described behaviour is implemented.