nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

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

srinivasan radhakrishnan

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.

Thanks.

Accepted answers

Nic Brough -Adaptavist-

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

All comments

Nic Brough -Adaptavist-

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

Dmitry Pashkevich

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 https://jira.atlassian.com/browse/JRA-4742

Dmitry Pashkevich

Possible duplicate https://answers.atlassian.com/questions/185527/issue-created-notification-for-specific-issue-type

Dmitry Pashkevich

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!

Vladimir Horev - RaleyApps

We made a notification plugin where you can define which notifications should be sent out based on whether issue matches specific JQL criteria https://marketplace.atlassian.com/plugins/net.vacom.jirassimo

This article explains how to configure notifications per issue type

And this - how to notify when on issue status transition

Have a look,

Vlad

JonasC

Hi,

I created this plugin: https://marketplace.atlassian.com/manage/plugins/net.koncis.atlassian.issue-type-notification-schemes

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.

Andrew King

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?

Jonas Mørup Chr

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: http://koncis.net/issue-type-ns.html

Andrew King

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.