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

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

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. 

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.

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.

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?

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

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';

It will be good to have this feature as every time we updated our staging server and this triggers the subscription emails which put users in to confusion.
I wish we could have this feature in 5.2.3 JIRA version.
Thank You
Sachin

We are also interested in this feature. We have a number of terminated users running subscriptions - some as many as 5, and we cannot remove them. This should be something an administrator can do when making a user inactive.

I'm with Yuriy on this one – we have many terminated users who have subscriptions running, and we can't stop them. It means our mail queue slows down trying to find non-existent email addresses.

Lack of this administrative feature causes dirt in log files from disabled users' subscriptions.

You do need an administrative function to be able to delete subscriptions.
We had a problem subscription (was causing mail queue to fill up) - and we had to go to the database to delete it.... :-o
-Nick

At the moment when deleting a filter JIRa tells you that there are subscriptions owned by others which will also be deleted when the filter is deleted. Choosingto delete causes JRA-7407.

Are you saying that we should add a new feature (improvement) to allow the owners of a filter to delete other users' subscriptions without deleting the actual filter?