View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0011993||mantisbt||api soap||public||2010-06-04 09:39||2018-05-20 07:01|
|Target Version||Fixed in Version|
|Summary||0011993: trigger events when bug added etc via soap|
Currently no events are triggered, causing hooks by plug-ins to fail
|Tags||No tags attached.|
|parent of||0013498||acknowledged||EVENT_REPORT_BUG not raised via SOAP API|
|has duplicate||0013436||closed||vboctor||Add note through soap doesn't trigger email notifications|
|has duplicate||0021557||closed||atrol||Issue creation events are not triggered when adding issues via SOAP API|
|has duplicate||0023666||closed||dregad||mc_issue_add does not trigger EVENT_REPORT_BUG/EVENT_REPORT_BUG_DATA event in plugin associated to bug creation|
|related to||0020578||new||move some events into core API|
|Not all the children of this issue are yet resolved or closed.|
@jreese : any ideas on how we should go about doing this?
It appears that creating/modifying issues through the SOAP API doesn't trigger any notification e-mails either.
Is that caused by this issue, or should I open a separate issue that problem?
@thijsputman : there's no need to open a separate issue, we'll track all events using this one.
Rombert: surely this is just a case evaluting the positioning of hooks so that the hooks are consistent? i.e. I assume that the soap api doesn't block/disable the event hooks/plugins, so if event's are not getting fired, it feels like we've got events in the wrong place...
Usually the SOAP API needs to fire the plugin events itself since the web UI triggers them directly as well.
There are different types of events, i think they could be classified on these two groups:
Most events are of type 1, and makes sense on the web frontend.
I think those should be moved into the core api. For the current issue, soap api ideally would call core api functions, soif the events are defined there, the behaviuor would be consistent.
(On a related issue, email notifications may have the same problem, since they are triggered from the caller, not the actual performer of the action)
Unassigned after a long time of inactivity.
|2010-06-04 09:39||AboeBakr||New Issue|
|2010-06-04 10:04||rombert||Assigned To||=> rombert|
|2010-06-04 10:04||rombert||Status||new => acknowledged|
|2010-06-04 10:04||rombert||Note Added: 0025706|
|2010-06-04 10:05||rombert||Target Version||=> 1.3.0-beta.1|
|2010-09-02 11:13||thijsputman||Note Added: 0026556|
|2010-09-02 15:49||rombert||Note Added: 0026557|
|2011-10-24 04:54||atrol||Relationship added||parent of 0013436|
|2011-11-09 02:43||rombert||Relationship added||parent of 0013498|
|2012-06-16 20:08||vboctor||Relationship replaced||has duplicate 0013436|
|2014-06-01 17:38||grangeway||Note Added: 0040709|
|2014-08-22 04:47||rombert||Note Added: 0041111|
|2014-12-08 02:10||atrol||Target Version||1.3.0-beta.1 => 1.3.0-beta.2|
|2015-03-15 19:59||dregad||Target Version||1.3.0-beta.2 => 1.3.0-beta.3|
|2015-09-06 17:47||vboctoradmin||Target Version||1.3.0-beta.3 => 1.3.0-rc.1|
|2016-01-12 03:43||atrol||Target Version||1.3.0-rc.1 => 1.3.0-rc.2|
|2016-02-07 18:07||cproensa||Note Added: 0052475|
|2016-02-07 18:08||cproensa||Note Edited: 0052475||View Revisions|
|2016-02-07 19:50||cproensa||Relationship added||related to 0020578|
|2016-06-12 02:37||atrol||Target Version||1.3.0-rc.2 => 1.3.0|
|2016-07-10 07:57||atroladmin||Target Version||1.3.0 => 1.3.1|
|2016-07-11 15:38||atrol||Target Version||1.3.1 =>|
|2016-07-28 01:32||atrol||Relationship added||has duplicate 0021557|
|2017-11-23 09:26||dregad||Relationship added||has duplicate 0023666|
|2018-05-20 07:01||atrol||Assigned To||rombert =>|
|2018-05-20 07:01||atrol||Note Added: 0059877|