Project specific email notifications does not work with source-integration

[libregeek]

Source Control Integration Plugin does not respect the custom email notifications configured for a particular project.

For example, consider a project has an Email Notification Configuration which allows all the Developers(role) to receive email notifications when an issue is Resolved. The notifications are NOT sent to Developers and only the reporter and administrators receives the notification.

However, the notifications are sent to Developers when an issue is resolved through the Mantis Web Interface.

[bright-tools]

The bug_resolve() API function handles e-mail notifications (and twitter), however source integration assigns the status of the bug directly rather than using this API. I'll take a look at what's required to address this.

[dregad]

Thanks for looking into it.

[bright-tools]

@Degrad, the change to address this and #80 are both in the same area. If you can let me know whether you're happy to merge #80 or not, I'll base the change either on that or the current code.

[dregad]

@bright-tools I just pushed a fix for #80, so if you'd like to propose a solution for this based on current master branch, it would be great.

[bright-tools]

@dregad I will take a look.

[dregad]

@bright-tools have you been able to make any progress on this ?

[dregad]

ping @bright-tools

[bright-tools]

@dregad Would you mind taking a quick look at https://github.com/bright-tools/source-integration/tree/iss22 ? I've not yet tested it, but I'd like your opinion on whether you're satisfied with the approach. Cheers!

[dregad]

@bright-tools it looks good to me, although I haven't actually tested the code. I would just rename $t_resolved to $t_resolve to follow the same semantics as $t_update (reflecting the fact that it's an action to take, vs a state)

[bright-tools]

@dregad Thanks. I'll rename & so long as it looks generally OK, I'll do some testing before I submit a PR.

[dregad]

@bright-tools Any progress on your testing ?