Best configuration for JETI to inform externals about changes?

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?

1 answer

1 accepted

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

one template and associate it with the Context

I have tried that, but that meant that the same template is used for different events, so I get the same information (like Issue created) for different events. At least I did not find the right approach here. I will try it again to ensure that I have understood it well enough ...

JETI Notification schemes like JIRA's ones are reusable

which is true, but we need it at the moment only for one project.

...

Please note that there is the Default event that matches all events not yet added to the Notification scheme.

I have tried that as well, but was not content with it. I will try it again, with a play project where the normal notification of JIRA is switched off.

I have now used a play project, and configured it the following way:

  • Defined a new notification template.
  • Added there as event only "Default" and as template "Use template from context".
  • Added then the context for the project, and added there as value only "Notification Template" (not "Template").

However, I get now on every change the same email, which is taken from "Create" template. So I will stick to my solution ...

Thank's for adding the request ticket, I think it is a reasonable one.

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

3,308 views 14 20
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot