Best configuration for JETI to inform externals about changes?

Question

We have bought lately "JIRA Email This Issue" (JETI) lately to support the requirements of one of our customers:

* They are not registered as users in JIRA (only one of them).
* But a list of people (== external email addresses) have to be informed about every change.

I have now tried some time to find a good (KISS) configuration, but the best I could find is:

* Define for each relevant event type a template.
* Define one notification scheme for that project.
* Register all events (one by one) to the template, and include in each notification event the list of users to be informed.

I tried to not use at all templates, but then the whole thing does not work.

What I don't like about the solution is:

* I have duplicated the normal notification scheme (more or less).
* I have duplicated the list of recepients.

I tried to use the default, but that takes all the time the same template, which does not fit well.

Is there a better solution available?

Tibor Hegyi [META-INF] · Accepted Answer

Hi Markus,

Let me answer your points.

Define for each relevant event type a template

It not necessary to define different templates for each event types. You can create one template and associate it with the Context. Then if you don't select a template in the Event configuration page, JETI will use the template selected in the Context.

Define one notification scheme for that project.

JETI Notification schemes like JIRA's ones are reusable. You simply associate multiple Contexts with the same Notification. This means no duplication of Notification schemes is necessary.

Register all events (one by one) to the template, and include in each notification event the list of users to be informed

I have duplicated the list of recepients.

This is true. You'll have to add recipients for each event. This not more cumbersome than what you must be used to with JIRA Notification Schemes. But I agree it would be easier if you could group events and configure them once. Please note that there is the Default event that matches all events not yet added to the Notification scheme. It may help you a bit.

I have create a feature request ticket for you that you can watch for progress.

This is how you can configure JETI at the moment.

Cheers,
Tibor