Details

    • Feedback Policy:

      JIRA feedback is collected from a number of different sources and is evaluated when planning the product roadmap. If you would like to know more about how JIRA Product Management uses customer input during the planning process, please see our post on Atlassian Answers.

    • Current Status:
      Hide
      Atlassian Update – 28 November 2017

      Hi everyone,

      Thank you so much for all your votes and comments on this suggestion. Your feedback has really helped us better understand the varied challenges you face with Jira notifications. My apologies for taking this long to provide an update on such a highly voted suggestion. Thank you for your patience!

      Despite our lack of communication, Jira notifications has actually been an area that we continue to explore. I would like to provide you with an update on this suggestion.

      When we explored this area in the past, we were looking to tackle a broad set of problems that resulted in very complex solutions. And these solutions carried with them a huge amount of risk and potentially jeopardized the evolution of other areas of the product. This time, we've taken a different approach.

      Over the past few months, we have explored this area in more detail. How are Jira notifications being used by various roles within an organization? How does the size of the organization impact the nature of issues faced with notifications?
      In the process, we've interviewed a vast range of users to gain additional insights.

      Amongst others, there was one challenge that stood out as it applies to almost all user types and organisation sizes. In common cases like issue inline edit, Jira generates an unnecessary volume of email notifications. Most of the notifications individually have little or no value, and it makes it really difficult for users to track changes.
      We've also learned a variety of ways how customers have been trying to deal with this problem, like creating variety of email filters trying to distinguish these valuable notifications. These attempts also generates multiple challenges.

      As we have explored solutions, there are two approaches we could take:

      1. Make it easier to handle the volume of notifications we generate. For instance, by giving an ability to customise email subject.
      2. Solve the core problem by reducing the volume of email notifications

      Based on our findings, we are going to pursue option #2.

      Our next steps are to explore options for solving these challenges, validate them with you, our customers, and prioritize the most impactful changes for development.

      Thank you again for all your feedback on this suggestion and we look forward to providing you with more updates as we work to improve Jira notifications!

      Cheers,
      Jakub Lazinski
      Product Manager, Jira Server

      Show
      Atlassian Update – 28 November 2017 Hi everyone, Thank you so much for all your votes and comments on this suggestion. Your feedback has really helped us better understand the varied challenges you face with Jira notifications. My apologies for taking this long to provide an update on such a highly voted suggestion. Thank you for your patience! Despite our lack of communication, Jira notifications has actually been an area that we continue to explore. I would like to provide you with an update on this suggestion. When we explored this area in the past, we were looking to tackle a broad set of problems that resulted in very complex solutions. And these solutions carried with them a huge amount of risk and potentially jeopardized the evolution of other areas of the product. This time, we've taken a different approach. Over the past few months, we have explored this area in more detail. How are Jira notifications being used by various roles within an organization? How does the size of the organization impact the nature of issues faced with notifications? In the process, we've interviewed a vast range of users to gain additional insights. Amongst others, there was one challenge that stood out as it applies to almost all user types and organisation sizes. In common cases like issue inline edit, Jira generates an unnecessary volume of email notifications. Most of the notifications individually have little or no value, and it makes it really difficult for users to track changes. We've also learned a variety of ways how customers have been trying to deal with this problem, like creating variety of email filters trying to distinguish these valuable notifications. These attempts also generates multiple challenges. As we have explored solutions, there are two approaches we could take: Make it easier to handle the volume of notifications we generate. For instance, by giving an ability to customise email subject. Solve the core problem by reducing the volume of email notifications Based on our findings, we are going to pursue option #2. Our next steps are to explore options for solving these challenges, validate them with you, our customers, and prioritize the most impactful changes for development. Thank you again for all your feedback on this suggestion and we look forward to providing you with more updates as we work to improve Jira notifications! Cheers, Jakub Lazinski Product Manager, Jira Server

      Description

      I would like to suggest the following imoprovments to the email notification:

      1. Have the ability to configure the notifcation period (eg. 10 minutes). Then every period the outstanding notifcations are proccessed and sent. To notifcation service should combine all updates for a single issue made by the same jira user into one email. This would reduce the volume of email notification. It is a real pain when you make 3 quick changes to a jia issue and this generates 3 emails. Thie more redundant emails jira sends the less likely people will read all of them.
      2. Jira still sends emails to me when I have made the change. Surely this should be able to turned of at least under my profile settings. (eg. "Don't notify me of change I make" ).

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                perrottg Greg Perrott
              • Votes:
                1186 Vote for this issue
                Watchers:
                516 Start watching this issue

                Dates

                • Created:
                  Updated: