View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0013498||mantisbt||api soap||public||2011-11-08 20:56||2023-05-25 15:03|
|Status||closed||Resolution||no change required|
|Summary||0013498: EVENT_REPORT_BUG not raised via SOAP API|
The event is coded into the user update code not the core api code. It should be raised whenever a new event is created not just via the HTML interface.
|Steps To Reproduce|
To end of function create in core/bug_api.php
|Tags||No tags attached.|
|related to||0023998||closed||vboctor||Implement |
|has duplicate||0015235||closed||rombert||Reporting an issue via the SOAP API does not trigger event EVENT_REPORT_BUG|
|related to||0020578||new||move some events into core API|
|child of||0011993||acknowledged||trigger events when bug added etc via soap|
I think it's the right decision to move the code, but there will be problems with existing plugins.
What will happen if a plugin like timecard  is installed and a bug is created via SOAP API?
Maybe there are other plugins which generate HTML output when hooking EVENT_REPORT_BUG, ....
Another side effect I found: After the suggested change the EmailReporting Plugin  will signal two times EVENT_REPORT_BUG
(In reply to comment 0013498:0030204)
All of these are good points. This is why the parent issue is targeted for 1.3.
Issue creation has been refactored to use
EDIT (dregad): see 0023998 - fixed in 2.13.0
We are resolving this issue as "no change required", because it was reported against an old version of MantisBT which is no longer supported.
We recommend that you upgrade to the latest stable version ; if after doing so the problem still exists, do not hesitate to reopen the issue.