View Issue Details

WikiJump to Notes
IDProjectCategoryView StatusDate SubmittedLast Update
0015559mantisbtplug-inspublic2013-03-03 07:452013-03-22 09:32
Reporterrct Assigned Toatrol  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionduplicate 
Product Version1.2.14 
Summary0015559: EVENT_UPDATE_BUG triggers missing
Description

Hello,

Like title said the event EVENT_UPDATE_BUG should be fired in some places it is not:

  • Group actions don't trigger EVENT_UPDATE_BUG
  • In the View Issue Details page when Change status to is set to Resolved, Closed (or Reopened?) the EVENT_UPDATE_BUG should be triggered before bug is saved to the database

Documentation excerpt:
EVENT_UPDATE_BUG (Chain)
This event allows plugins to perform both pre- and post-processing of the updated bug data structure after being modified by the user, but before being saved to the database.

Additional Information

=> in bug_actiongroup.php EVENT_UPDATE_BUG should be fired every time it's commented "/* @todo we need to issue a helper_call_custom_function( 'issue_update_validate', array( $t_bug_id, $t_bug_data, $f_bugnote_text ) ); /"
=> in bug_update.php the EVENT_UPDATE_BUG should be fired before the Resolved/Closed/Reopened code modify the bug in the database

TagsNo tags attached.

Relationships

Relationship GraphDependency Graph
duplicate of 0014897 acknowledged Plugins events features request 

Activities

rombert

rombert

2013-03-03 11:44

reporter   ~0035364

Definitely not a blocker
rct

rct

2013-03-03 11:53

reporter   ~0035365

I've put "block" because it prevent to build a reliable plugin which catch bug's updates.
rct

rct

2013-03-08 12:15

reporter   ~0035423

Nice, I wanted it so much :)

Thank you!
atrol

atrol

2013-03-11 16:51

developer   ~0035432

rct, patches are welcome. It all comes to priority and a dev or community member deciding to spend their time on a specific issue.

Submitting a patch is always a good idea, as it increases the chances of improvement eventually making it into MantisBT core. All contributions are welcome and greatly appreciated.

Patch submissions can be made in several ways. In the order of preference:

  1. Send us a Pull Request on our Github repository [1]
  2. Attach a GIT patch to the issue
  3. Attach a Unified Diff, clearly specifying the patch's base release

Kindly avoid to upload entire modified PHP files.

Please make sure that your submissions adhere to our Coding Guidelines [2], if they don't your patch might be rejected.

[1] https://github.com/mantisbt/mantisbt
[2] http://www.mantisbt.org/wiki/doku.php/mantisbt:coding_guidelines