How to configure Notification scheme based on Issue Type or Status in "On demand JIRA"

Hi All,

I have new goal for configuring JIRA notification for a project based on "Status" and "Issue Types". Could you pls give the setps to achieve my goal.


4 answers

1 accepted

10 votes
Accepted answer

You can't do this at a scheme level. Notifications schemes belong to projects, not issue types.

What you can do though:

  • For each issue type, create a new workflow
  • For each transition within each workflow, decide what notifications you need when the transition happens (remember that a transition moves an issue from one status to another)
  • Once you have the list of notifications needed, create a custom "event" for each one
  • Go back into your workflows and tell them to fire your custom events as appropriate
  • Finally, amend the notification scheme to send the emails for your custom events to the people they need to go to

While the suggested workaround is viable, it's a lot of work to do and not really scalable (have to create tons of custom events for each issue type).

Please vote for this (and possibly related) feature request

Don't forget to make sure that the "Create Issue" transition has a "Re-index" post-function, otherwise the created issues will not appear in search!

We made a notification plugin where you can define which notifications should be sent out based on whether issue matches specific JQL criteria 

Have a look,




I created this plugin:

By defining notification schemes as usual, you can create (with the plugin) issue type notification schemes, and thereby map issue types to notification schemes.

I hope that helps you all.

Please let me know if you find any problems using it.


Has anyone tried this yet? I installed an evaluation version and created an issue type notification scheme. Am trying to figure out how to swap out an existing project notification scheme and use this instead. I associated the project with the Issue Type Notification scheme, and got a warning about double emails. How do I de-associate the other one?

Hi there.

You need to remove the notification scheme you have on your project, and use the issue type notifications schemes instead.

The issue type notifications schemes then basically uses your original notifications schemes underneath in the mapping from issue type -> scheme.

Som doc here:

Okay, thanks I figured it out. You need to change the project's initial associated notification scheme to <none> to avoid the double emails, correct? Then associating the new Issue Type Notification Scheme to the project instead will work correctly.

One more question - we have installed the add on, and applied it to one project. It does not look possible to associate a particular Issue Type Notification Scheme with multiple projects. can you confirm this please? That is essential for us.



You should be able to select multiple projects in the drop down of the association to projects. Hold down ALT, or maybe is it SHIFT, while clicking the projects in the select box

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 29, 2018 in Jira

How to set up an incident workflow from the VP of Engineering at Sentry

Hey Atlassian community, I help lead engineering at Sentry, an open-source error-tracking and monitoring tool that integrates with Jira. We started using Jira Software Cloud internally last year, a...

1,089 views 0 8
Read article

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