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

Shared Filter Management - subscriptions

XMLWordPrintable

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

      Updated 21 December 2015

      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; however there are not currently any plans to implement this suggestion.

      Please remember that jira.atlassian.com is one of many inputs for the JIRA roadmap. You can learn more about our process here.

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

      Danke Schoen,
      Otto Ruettinger
      Principal Product Manager, JIRA
      oruettinger (at) atlassian (dot) com

      Updated Description
      As a founder admin, I want to be able to;

      • see all the users that are subscribed to a filer.
      • manage which users are subscribed to a filter.
      • delete filters even if I am not the filter creator.

        1. 07-01-2016 14-12-59.png
          07-01-2016 14-12-59.png
          38 kB
        2. screenshot-1.png
          screenshot-1.png
          27 kB

            [JRASERVER-7404] Shared Filter Management - subscriptions

            Anton Kolin [Teamlead] added a comment -

            https://marketplace.atlassian.com/apps/1215065/subscriptions-for-jira-filter-manager

            Anton Kolin [Teamlead] added a comment - https://marketplace.atlassian.com/apps/1215065/subscriptions-for-jira-filter-manager

            Mike Hang added a comment -

            Now 150 votes.

            Mike Hang added a comment - Now 150 votes.

            Nathanael Motz added a comment -

            I'm with Shawn Odegaard. Do the right thing. Don't F the customer Atlassian.

            Nathanael Motz added a comment - I'm with Shawn Odegaard. Do the right thing. Don't F the customer Atlassian.

            Chris Bellar added a comment -

            This seems like such a basic function that it's unbelievable that this hasn't been accomplished in all this time.Just because it's not a flashy change doesn't mean it's not needed. 

            Chris Bellar added a comment - This seems like such a basic function that it's unbelievable that this hasn't been accomplished in all this time.Just because it's not a flashy change doesn't mean it's not needed. 

            Shawn Odegaard added a comment -

            Agreed. Subscriptions are by far the hardest thing to manage. It seems like it would be truly simple to build a tool just like the shared filter and shared dashboard so that we can manage these.

            If there was even a way that a user could see their own subscriptions that would be a step forward because we could log in as that user and disable it as them.

            Do the right thing.

            Shawn Odegaard added a comment - Agreed. Subscriptions are by far the hardest thing to manage. It seems like it would be truly simple to build a tool just like the shared filter and shared dashboard so that we can manage these. If there was even a way that a user could see their own subscriptions that would be a step forward because we could log in as that user and disable it as them. Do the right thing.

            PB03873 added a comment -

            Is it so difficult to include this request suggested more than 10 years ago and supported by 50+ administrators ? Do you realise the pain it is for us everyday ?

            To give a concrete example, I added screen shot ( ). It only relates to a single project and we have hundreds of projects. Users create e-mail subscriptions in order to be updated on the latest changes (very nice feature in itself). The problem is that we are outsourcing a lot and therefore have a lot of turn-over. The result is hundred and hundred of non-delivery notifications which are cluttering our mailboxes, hiding the real meaningful messages.

            PB03873 added a comment - Is it so difficult to include this request suggested more than 10 years ago and supported by 50+ administrators ? Do you realise the pain it is for us everyday ? To give a concrete example, I added screen shot ( ). It only relates to a single project and we have hundreds of projects. Users create e-mail subscriptions in order to be updated on the latest changes (very nice feature in itself). The problem is that we are outsourcing a lot and therefore have a lot of turn-over. The result is hundred and hundred of non-delivery notifications which are cluttering our mailboxes, hiding the real meaningful messages.

            Otto added a comment -
            21 December 2015

            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; however there are not currently any plans to implement this suggestion.

            Please remember that jira.atlassian.com is one of many inputs for the JIRA roadmap. You can learn more about our process here.

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

            Regards,
            Otto Ruettinger
            Principal Product Manager, JIRA
            oruettinger (at) atlassian (dot) com

            Otto added a comment - 21 December 2015 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; however there are not currently any plans to implement this suggestion. Please remember that jira.atlassian.com is one of many inputs for the JIRA roadmap. You can learn more about our process here . I understand that our decision may be disappointing. Please don't hesitate to contact me if you have any questions. Regards, Otto Ruettinger Principal Product Manager, JIRA oruettinger (at) atlassian (dot) com

            Adam Nichols (DISH) added a comment -

            Considering this issue has been open now since 2005, does this mean JIRA does not actually listen to it's customers or care about our feedback or concerns?

            Adam Nichols (DISH) added a comment - Considering this issue has been open now since 2005, does this mean JIRA does not actually listen to it's customers or care about our feedback or concerns?

            m added a comment -

            A simple active flag in the DB would achieve this - and allow easy disabling per subscription?

            m added a comment - A simple active flag in the DB would achieve this - and allow easy disabling per subscription?

            European Directories Operations added a comment -

            You can clean-up using SQL on the underlying datastore if it's a DB.

            This is what worked for me (our users are managed by Crowd):

            DELETE filtersubscription FROM filtersubscription JOIN cwd_user ON cwd_user.user_name = filtersubscription.username WHERE cwd_user.active='F';

            European Directories Operations added a comment - You can clean-up using SQL on the underlying datastore if it's a DB. This is what worked for me (our users are managed by Crowd): DELETE filtersubscription FROM filtersubscription JOIN cwd_user ON cwd_user.user_name = filtersubscription.username WHERE cwd_user.active= 'F' ;

              Unassigned Unassigned
              mike@atlassian.com Mike Cannon-Brookes
              Votes:
              162 Vote for this issue
              Watchers:
              94 Start watching this issue

                Created:
                Updated: