View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0017765 | mantisbt | api soap | public | 2014-10-15 03:27 | 2014-10-22 03:27 |
Reporter | vboctor | Assigned To | vboctor | ||
Priority | normal | Severity | minor | Reproducibility | have not tried |
Status | assigned | Resolution | open | ||
Product Version | 1.2.18 | ||||
Summary | 0017765: mc_issue_update() notifications inconsistent with web | ||||
Description | It seems we generate different email notifications based on the code path that is followed: For the scenario where the issue is updated to reflect assignment to user and status becoming resolved, resolution becoming fixed. Option 1: Notification will be "issue is resolved" or "issue is closed" based on status. I would say option 1 notification makes sense. The logic for that is in bug_update.php rather than the BugData->update() method. I've marked this as a SOAP API issue, since in case of the SOAP API we have no equivalent of "change status" page. We only have the update, so there is no work around. But it impacts both. | ||||
Tags | No tags attached. | ||||