Uploaded image for project: 'Jira Cloud'
  1. Jira Cloud
  2. JRACLOUD-4742

Being able to create notification groups based by "Issue Type"



    • 90
    • 48
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.


      NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.

      Atlassian Update – 4 January 2016

      Hi everyone,

      Thanks for voting and commenting on this issue. Your feedback is key to helping us understand how you use JIRA so we can continue improving your experience. We have reviewed this issue over the last few days.

      Improving notifications in JIRA is a key area that we intend to address as soon as possible. It's important to us that we not only improve JIRA notifications, but also work towards more consistency between JIRA and other Atlassian applications like Confluence and Bitbucket.

      While we can't provide a concrete timeline, rest assured that this is something we are actively thinking about this across Atlassian and plan to invest in as soon as it's feasible.

      It's important to understand that we rarely try to implement individual features from jira.atlassian.com, but instead take a holistic look at the problem and use feedback from the comments here and a dozen other sources of customer input to solve the core problems.

      Please don't hesitate to contact me if you have any questions or feedback.

      Dave Meyer
      Product Manager, JIRA Platform

      Being able to create notication groups based by "Issue Type".

      let's say for example I would like to create an issue type "Business Feature", and have a group of people "Business Feature Group", so when any issue related to "Business Feature" type is created etc... notification is sent to the group "Business Feature Group".
      and so on...


        Issue Links



              Unassigned Unassigned
              8c443ef4a4c3 Vadim Shaykevich
              345 Vote for this issue
              192 Start watching this issue