View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0022676 | mantisbt | feature | public | 2017-04-06 05:10 | 2017-04-18 03:36 |
Reporter | doker | Assigned To | |||
Priority | normal | Severity | major | Reproducibility | always |
Status | new | Resolution | open | ||
Product Version | 2.3.0 | ||||
Summary | 0022676: Don't change status | ||||
Description | Hello! This begin after update to version 2.3.0 | ||||
Tags | No tags attached. | ||||
Anybody have the same problem? |
|
doker, I was not able to reproduce your problem with a fresh install of 2.3.0. You should provide detailed step-by-step instructions to reproduce the issue; the following additional information may also be useful:
Which version did you use before? |
|
step-by-step:
before we use version 1.3. Do you need my config_inc.php? |
|
I am not complete sure, but the issue might be caused by the changes in 0021203. |
|
@cproensa, maybe you can have a deeper look at it? |
|
The conditions on which the status change occurs are: The conditions needed for automatic change to 'bug_assigned_status' are:
At the described case, "current handler is empty" is not met, so the status change is not triggered. We could discuss if this condition is necessary. I'm not sure if removing that would present side effects for other scenarios. |
|
Exactly what I thought when looking at the code. |
|
Hi cproensa, thx for your response. Isn't good news for me, because in version 1.3 status was change if bug was be assing to other handler. How we can we revert this feature? Person 1 take ticket to youself, set status "comfitmed" and fixed part of bugs, then assign it to person 2 for continue, so person 2 will be see this bug in current status - "confirmed", but realy bug not confirmed by person 2. |
|
atrol, status "feedback" I explain as example. We can use status "comfirmed", the same problem. If bug in status "comfirmed" will be assing to other handler, status not change to "Assigned" |
|
So, can we revert this feature? Or maybe has workaround? |
|
? |
|
@doker you could remove the mentioned condition This would mean to search for the following line in core/bug_api.php (should be line 2160)
but keep in mind what @cproensa told
|
|
Great! |
|