View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0004652 | mantisbt | bugtracker | public | 2004-10-01 08:00 | 2013-02-25 23:01 |
Reporter | xbromy | Assigned To | thraxisp | ||
Priority | normal | Severity | minor | Reproducibility | always |
Status | closed | Resolution | fixed | ||
Product Version | 0.19.0 | ||||
Fixed in Version | 0.19.1 | ||||
Summary | 0004652: Fixed in Version not applyed to Bug at CLOSE | ||||
Description | The fixed_in_version value is not applyed to the bug at close in the bug_update.php in: | ||||
Tags | No tags attached. | ||||
case CLOSED: bug_close updates the status and bugnote and sends message----fix start---- bug_close( $f_bug_id, $f_bugnote_text ); break; |
|
How did you find this problem? In bug_change_status_page, the fixed in version is not visible if the bug is going directly to the closed status. If in the same page, you are going to resolve it and close the bug immediately, the resolve action will pick up the status. From the bug_update*_page, all fields are updated. |
|
when you have a bug and set the status to resolved but you leave the fixed_in_version open. and if you then go to the bug and click on change status to closed your're getting the page like the "resolve page" but for "close" and then the data "fixed_in_version"+"closed text" are submittet to the update_bug.php where my 0.19.0 code is: case CLOSED: bug_close updates the status and bugnote and sends messagebug_close( $f_bug_id, $f_bugnote_text ); <-- here is only the status and text |
|
Fixed in CVS. All changes not go through bug_api:bug_update where any changes are logged. This eliminates a dependency on bug_update.php knowing what fields are listed in bug_change_status_page.php. |
|