How do I send a notification based on custom issue type?

I've looked at https://confluence.atlassian.com/display/JIRAKB/How+To+Send+Notifications+By+Issue+Type and https://confluence.atlassian.com/display/JIRA/Adding+a+custom+event, which is very helpful. But the Events seems to be targeting issue event (issue create, issue updated, etc) vs issue type (Bug, New Feature, etc). Please let me know if it is possible to send out notifications when a certain issue type, like when a Bug or New Feature is created, not on issue events. Thanks in advance.

3 answers

1 votes

Yes and no.

There are two types of thing you can to to an issue.

  1.  An action - these update the issue in some way, but do not move it on in the process (workflow).  Editing an issue, commenting on it, reassigning it, cloning, deleting, logging work, etc.  These actions have nothing to do with the type of the issue, they apply to all issues.  The can be allowed/prevented by permissions and so-on, but they do the same thing - an edit is an edit, a worklog is a worklog...
  2. transition - these change the status of an issue.  Including "issue does not exist" -> "issue is new".   A workflow is a description of all the possible transitions.  The workflows can be set by project and issue type, and every transition has a "fire event" post-function.  So you could define different workflows that fire different events for "issue created" for each different case you need.

 

 

Nic is correct in his explanation.  Another alternative is to set up a filter that looks for new issues of a specific type created in the past "x" minutes.   Run a subscription at that same (or shorter) interval and you can get an email sent when those new issues appear.   But it is not an immediate notification (as is Nic's transition suggestion)

Hi,

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

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

For instance, Stories goes to project leader, bugs to Support Team, and so on.

I hope that helps you all.

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

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,039 views 13 18
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