View Issue Details

IDProjectCategoryView StatusLast Update
0017765mantisbtapi soappublic2014-10-22 03:27
Reportervboctor Assigned Tovboctor  
PrioritynormalSeverityminorReproducibilityhave not tried
Status assignedResolutionopen 
Product Version1.2.18 
Summary0017765: mc_issue_update() notifications inconsistent with web
Description

It seems we generate different email notifications based on the code path that is followed:
Option 1: Change status update page.
Option 2: Bug update page.
Option 3: mc_issue_update()

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.
Option 2 and 3: Notification will be "issue is assigned".

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.

TagsNo tags attached.

Activities

There are no notes attached to this issue.