View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0032861 | mantisbt | code cleanup | public | 2023-08-25 12:16 | 2025-12-18 11:23 |
| Reporter | dregad | Assigned To | |||
| Priority | high | Severity | minor | Reproducibility | N/A |
| Status | new | Resolution | open | ||
| Summary | 0032861: Implement IssueUpdateCommand | ||||
| Description | Implement IssueUpdateCommand and use it from the appropriate places in the code. There are discrepancies between issue updates from the GUI vs the API, as bug_udpate.php has not been kept in sync with mc_issue_update(). One confirmed case is the latter does not check for child relationships when resolving an issue (see https://github.com/mantisbt/mantisbt/pull/1906#issuecomment-1693602387). | ||||
| Tags | No tags attached. | ||||
|
There was a community attempt to do this, see PR https://github.com/mantisbt/mantisbt/pull/1400 |
|
|
MantisBT: master 007e3f1a 2023-08-26 06:30 Details Diff |
Prevent API resolving parent with unresolved children There are discrepancies between issue updates from the GUI vs the API, as bug_udpate.php has not been kept in sync with mc_issue_update(). This is a quick fix for one of these occurrences; REST/SOAP API allowed mc_issue_update() to resolve a parent Issue having unresolved children while the GUI does not (unless $g_allow_parent_of_unresolved_to_close is ON). The proper, long-term solution to this problem is to implement a new IssueUpdateCommand to ensure consistent behavior (see Issue 0032861). Fixes 0032860 |
Affected Issues 0032860, 0032861 |
|
| mod - api/soap/mc_issue_api.php | Diff File | ||
|
MantisBT: master-2.25 37f65a58 2023-08-26 06:30 Details Diff |
Prevent API resolving parent with unresolved children There are discrepancies between issue updates from the GUI vs the API, as bug_udpate.php has not been kept in sync with mc_issue_update(). This is a quick fix for one of these occurrences; REST/SOAP API allowed mc_issue_update() to resolve a parent Issue having unresolved children while the GUI does not (unless $g_allow_parent_of_unresolved_to_close is ON). The proper, long-term solution to this problem is to implement a new IssueUpdateCommand to ensure consistent behavior (see Issue 0032861). Fixes 0032860 (cherry picked from commit 007e3f1aecac0b804f101dc40df82d03f395def0) |
Affected Issues 0032860, 0032861 |
|
| mod - api/soap/mc_issue_api.php | Diff File | ||