We receive a lot of maintenance announcements of service providers to our RT instance. Most of them are being followed up with related messages (reminders/beginning/finished/etc.).
I have made an RT extension that matches up those follow-up mails to the original announcement. This works mostly well, but one thing is bothering me: even tough I the follow-ups are merged into the original ticket (by a global scrip) RT is executing later scrips (e.g. auto-reply / on open / etc.).
Is there any way to circumvent this behaviour? So far my searches turned up a ‘no’, but maybe I am missed something?
Would setting the ticket to open/resolved before merging it into the original (still open) ticket prevent the new-ticket scrips to be running?
Any creative ideas/approaches to reduce the amount of mails received by external/non-owning recipients appreciated.