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

Ability For A User To Unsubscribe From A Group Subscription Filter

XMLWordPrintable

    • 1
    • 2
    • 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.

      Problem Definition

      When administrator creates a filter that subscribed to a group, but some user's don't want to receive its notifications, but at the same time admins do still want the subscription to email for everyone else.

      Suggested Solution

      Allow users to manage their own subscriptions..

            [JRASERVER-60160] Ability For A User To Unsubscribe From A Group Subscription Filter

            Gosia Kowalska added a comment -
            Atlassian Update – 9 August 2019

            Hi,

            Thank you for raising this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request.

            This is an automated update triggered by low user engagement with this suggestion (number of votes, number of watchers).

            We hope you will appreciate our candid and transparent communication and our attempts to become more transparent about our priorities. Making tradeoffs and saying no is never an easy task to perform. You can read more about our approach to highly voted server suggestions here.

            To learn more about our recent investments in Jira Server and Data Center, please check our two new dashboards containing Recently resolved issues and Current work and future plans.

            Regards,
            Jira Server and Data Center Product Management

            Gosia Kowalska added a comment - Atlassian Update – 9 August 2019 Hi, Thank you for raising this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request. This is an automated update triggered by low user engagement with this suggestion (number of votes, number of watchers). We hope you will appreciate our candid and transparent communication and our attempts to become more transparent about our priorities. Making tradeoffs and saying no is never an easy task to perform. You can read more about our approach to highly voted server suggestions here . To learn more about our recent investments in Jira Server and Data Center, please check our two new dashboards containing Recently resolved issues and Current work and future plans . Regards, Jira Server and Data Center Product Management

            Bill Tanner added a comment -

            Our user base would love this feature.

            We have a few all user email summaries, daily digest being one, that goes out. Some of our users don't want this / don't find it useful and would want the ability to unsubscribe from the subscription.

            I know I could create a new group and remove the requesting users, however this will create additional admin burden when creating new accounts as well as a lack of self service.

            Bill Tanner added a comment - Our user base would love this feature. We have a few all user email summaries, daily digest being one, that goes out. Some of our users don't want this / don't find it useful and would want the ability to unsubscribe from the subscription. I know I could create a new group and remove the requesting users, however this will create additional admin burden when creating new accounts as well as a lack of self service.

              Unassigned Unassigned
              somidi Sam Omidi (Inactive)
              Votes:
              3 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: