View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0010841 | mantisbt | administration | public | 2009-08-17 10:23 | 2010-02-22 14:34 |
Reporter | atrol | Assigned To | vboctor | ||
Priority | normal | Severity | major | Reproducibility | always |
Status | closed | Resolution | fixed | ||
Product Version | 1.2.0rc1 | ||||
Target Version | 1.2.0 | Fixed in Version | 1.2.0 | ||
Summary | 0010841: Target Version not cleared when Version is deleted | ||||
Description | "Fixed in Version" and "Product Version" are cleared in all issues where the version is referenced. However "Target Version" is not. The behaviour should be the same for all fields. Further enhancement: If a version is deleted, provide a mechanism who checks whether there are referenced issues. If yes, give the user the chance to:
| ||||
Tags | No tags attached. | ||||
We should be inserting a history item (example: 1.2 => ) for each bug where the versions are cleared. It should be possible to roll it into one SQL query. |
|
I thought about this, but I would like to track this as separate work (i.e. separate issue). The work in this issue was to get target version to parity with fixed_in_version and version. This is what I think we should do relating to updating the history.
Do we want to change the last updated timestamp? My gut feel here is no. |
|
Sounds fair to me. I agree with your points as well. |
|
MantisBT: master-1.2.x ba426dbb 2009-10-28 02:58 Details Diff |
Fixes 0010841: Target Version not cleared when Version is deleted. |
Affected Issues 0010841 |
|
mod - core/version_api.php | Diff File | ||
MantisBT: master c8a9d4a5 2009-10-28 02:58 Details Diff |
Fixes 0010841: Target Version not cleared when Version is deleted. |
Affected Issues 0010841 |
|
mod - core/version_api.php | Diff File |