Custom handler for send messages

[sramko]

Hi, I'm totally new to Jira and just evaluating the platform for a proof-of-concept on re problem we have here in the company.

I'm looking for a "handler" (so a programmable Java module/API) to process outgoing mails before they are send,

background:

We are using Jira Server, and additionally various other ticketing-systems throughout the organizations. Issue-resolution requires sometime the involvement of support-units which are not using Jira. Involvement is done though the ticketing-systems

I would like to check if it is possible to send and receive mails to and from the other ticketing-systems.

I found the great tutorial on Creating a custom email handler for Jira: with this I'm able to identify incoming mails from parse the other systems, distinguish them from mails coming from human users, parse the ID's of the tickets from the other system, and update the existing tickets accordingly.

problem:

Now I'm looking for a similar solution for outbound messages, which are send from Jira to the other systems:

The other systems, as well as our Jira, are configured to send receipt-confirmations. But this would end in a loop, which I would like to avoid. So, depending on the event and recipient I would like to be able to suppress the sending of messages.

Further, the other systems shall be able to identify messages related to existing tickets in the other systems. For that I need to identify if a message is send to a human or to another ticketing-system. And for the later I have to include the foreign system's ticket-id in the correct format in the message.

I was not able to find documentation on a "outgoing mail handler", similar to the linked "incoming mail handler" above. Does anyone know of a solution? Was I just to stupid to find it?

Thanks for your ideas!

-----

Update to the original post:

Would following approach bring a stable and reliable solution:

1. disable all notifications for the project
2. configure a webhook, which sends a request to another system on changes in the issues
3. perform calculation, checks and creation of message-text within the webhook-receiver  system
4. trigger sending of  message via REST for sending notifications related to issues

Too complicated and instable? Or would this look like a 'normal' approach?