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

Adding a user to a watchers list should cause an email notification

    XMLWordPrintable

Details

    • 11
    • 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.

    Description

      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.

      We've made the decision to close this request, as we do not reasonably expect to implement it in any future iteration of JIRA. Adding another event that triggers an email notification adds more complexity to JIRA's notification system. The existing options for notifying a user about an issue (using the Share button or @mentioning them in a comment) are sufficient in most cases and leverage existing patterns.

      I understand that our decision may be disappointing. Please don't hesitate to contact me if you have any questions.

      Regards,
      Dave Meyer
      dmeyer@atlassian.com
      Product Manager, JIRA Platform

      Adding (or removing?) a user from a watchers list should cause an email notification to that user.

      This feature is especially desirable due to the absence of the feature requested in JRA-5493 as you need to add watchers after an issue has been created.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              fe175279a289 Mick Hollins
              Votes:
              249 Vote for this issue
              Watchers:
              154 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: