Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-5494

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

XMLWordPrintable

    • 11
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? 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.

            [JRASERVER-5494] Adding a user to a watchers list should cause an email notification

            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3062514 ] New: JAC Suggestion Workflow 3 [ 3688558 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2619137 ] New: JAC Suggestion Workflow [ 3062514 ]
            Rachel Lin (Inactive) made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2592147 ] New: Confluence Workflow - Public Facing v4 [ 2619137 ]
            Status Original: Closed [ 6 ] New: Resolved [ 5 ]
            Ignat (Inactive) made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2361251 ] New: JIRA PM Feature Request Workflow v2 - TEMP [ 2592147 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 [ 2128813 ] New: JIRA Bug Workflow w Kanban v6 - TEMP [ 2361251 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2091666 ] New: JIRA Bug Workflow w Kanban v6 [ 2128813 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 [ 889705 ] New: JIRA Bug Workflow w Kanban v6 - TEMP [ 2091666 ]
            jonah (Inactive) made changes -
            Description Original: {panel:title=Atlassian Update – 4 January 2016|borderStyle=solid|borderColor=#ebf2f9 | titleBGColor=#ebf2f9 | bgColor=#ffffff}
            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
            {panel}

            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.             		New: {panel:bgColor=#e7f4fa}
              *NOTE:* This suggestion is for *JIRA Server*. Using *JIRA Cloud*? [See the corresponding suggestion|http://jira.atlassian.com/browse/JRACLOUD-5494].
              {panel}

            {panel:title=Atlassian Update – 4 January 2016|borderStyle=solid|borderColor=#ebf2f9 | titleBGColor=#ebf2f9 | bgColor=#ffffff}
            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
            {panel}

            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.
            jonah (Inactive) made changes -
            Link New: This issue relates to JRACLOUD-5494 [ JRACLOUD-5494 ]
            Confluence Escalation Bot (Inactive) made changes -
            Labels Original: JW-PLATFORM affects-server New: JW-PLATFORM affects-cloud affects-server

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

                Created:
                Updated:
                Resolved: