View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0004834 | mantisbt | bugtracker | public | 2004-11-08 18:50 | 2004-12-11 03:02 |
Reporter | packeteer | Assigned To | vboctor | ||
Priority | normal | Severity | minor | Reproducibility | always |
Status | closed | Resolution | fixed | ||
Product Version | 0.19.1 | ||||
Fixed in Version | 0.19.2 | ||||
Summary | 0004834: When you reopen an issue (after the issue has been RESOLVED), resolution is not set to REOPENED as it should be | ||||
Description | When you reopen an issue (after the issue has been RESOLVED), resolution is not set to REOPENED as it should be. In fact if you look in the Issue History, the resolution at reopen is set to REOPENED and then immediately set back to its previous value. To repeat the problem, resolve an issue with a resolution (e.g. fixed), close and then reopen it with a new assigned person. The issue resolution doesn't change to "reopened". The problem is due to a bug in bug_update.php. When an issue is reopened, function bug_reopen is firstly called which sets resolution to REOPENED. Then few lines of code down, function bug_update is called to update other fields such as AssignedTo etc... Unfortunately, function bug_update resets resolution from REOPENED to whatever its original value was. The fix is to add a line of code $t_bug_data->resolution = config_get( 'bug_reopen_resolution'); This will make sure that REOPENED resolution doesn't get reset by mistake.
| ||||
Additional Information | This bug is introduced in 19.1. It used to work fine in 19.0 | ||||
Tags | No tags attached. | ||||