|
Yes, that's the main problem. But the other stuff is also needed.
Especialy if you want to use some of the shared filters on the default dashboard. I'm aware of the schedule but I think that this particular issue is one thing you missed when implementing filters. > For now I would be greatfull to be able to adjust filters of deleted users. (maybe when deleting a user that has shared filter give the filters to jira-administrator?)
Dangling subscriptions for deleted users is an old bug that was fixed a while back ( Cheers, Cleaning it up will cause other problems.
A lot of are users are sharing filters. So if one of these users who shares filters is deleted then the filter shouldn't be deleted! I still want that filter. So like I said give the administrator the possibilitie to adjust and give a filter to somebody else Kristof,
I can see your point. We will leave this issue open to track this enhancement. Anton If and admin had the ability to 'take' and 'assign' ownership of a filter, everything else would come along naturally without any special support.
We have the same problem with our filters, so I would strongly suggest that (at least) the jira-administrator shall be able to completely manage all shared filters. What I do not understand is that atlassian has created those two global permissions:
But once the filter is created, no one can get it out of the system lest rename or change it. Please vote for it Many thanks Has this been scheduled or has there been any progress made on this? I have filters that hundreds of people are using that I created with an account I now need to get rid of. It would be nice to be able to transfer filters to another account.
We are finding this issue quite a problem at the moment, as filter subscriptions are being sent out from our UAT Jira instance. We could disable the SMTP server, but this is required for testing. The administrator should at least have the ability to disable subscriptions completely, if not the whole functionality suggested here.
We are facing this issue as the number of JIRA users grow in our environment as well.
What is the ETA on delivering this functionality? In the meantime, is there a workaround in place to remedy this issue? We could really do with this as well. We have a number of shared global filters on our installation. We have since opened it up to a number of our partners and there is no way to prevent these filters from being displayed to them.
Our Jira at XenSource has been up for a couple of years now, and the number of shared filters full of crud is a pain to manage. We've got to log in as each individual user (some of whom have left the company) and clean up their filters.
We have the problem that some users created USELESS filters and share them with all others.
Some users created the SAME filter and share them with all others.  The administrator must have the possibility to consolidate the collection of filters. VOTE FOR IT Guys,
I did some testing and found out that someone could could actually delete or modify a filter created by another user by just copying the "Delete" or "Save" link of any own filter and modifying the URL with the filterId of the other user. The only prerequisite I noticed was that the filter is visible for the own user, e.g. you must be in the same group whom the filter is shared with. Is that expected behaviour? I think, with that in mind, it should be fairly easy to just modify managefilters_shared.jsp to show at least the "Delete" link for shared filters. Best Regards I did some testing along the same lines as Andreas, and found that security is not enforced on editing shared filters. Even a user who doesn't have the necessary privileges to share filters can do so if they manually enter the necessary URL. While this is relatively difficult to do, it's not impossible. Also, ANY user can edit other's shared filters, simply by changing the ID in the URL. No administrator rights are required. While this doesn't affect any data, it can have the effect of hiding issues from view, either intentionally or unintentionally. This is a security risk, and needs to be fixed!
The way Jira handles filters right now is not very administrator-friendly. If I want to create a filter for everyone to use, I must create it under one particular user. If that user leaves the company or something, they will still own the filter. A filter for everyone to use (such as one on the dashboard) shouldn't be tied to one particular user.
Also, even worse, if a user creates a filter and shares it with everyone and then leaves the company, the filter is always on the dashboard portal page of public filters, and because that user is gone (and you can't login as them), you can never delete the filter from the main page that everybody sees! (Currently the saved filters portal does not allow the admin to say which filters will be published.) If the user is still at the company, you can figure out who owns the filter and ask them to delete it, but it's annoying as the admin to have to contact people and ask them to do trivial stuff. How will we know if/when this is on the roadmap and when we can expect this to be implemented?
Atlassian - can we please have some action on this.
Hi,
We are working on As part of this work we are also introducing the concept of Favourite Filters. This will allow each user to choose which filters they would like to see on various pages, such as Manage Filters page, and will solve the problem of overwhelming number of shared filters turning up everywhere in the interface. At the moment we do not have an implementation date for this feature, however we hope that Favourite Filters will help here. For more information on the way new features are scheduled please have a look at: Cheers, This is becoming a real administrative burden for us. Please allow Admins to unshare filters.
Out of interest, it's possible to re-assign filters to new users by changing the value of the Authorname column in the searchrequest table (JIRA v3.11). We've used this successfully to re-allocate filters.
Note there's also a Username column on the searchrequest table which is sometimes completed and also needs to be updated (this may be related to upgrading from an older JIRA version). Yes. I've tweaked that field before, and then you have to reindex, right? I believe the Username column is used to restrict who can see the filter, i.e. sharing. If the username is that same as the authorname then the filter is private.
The inability of an Administrator to edit or delete a shared filter feels like a very odd design decision.
It is very important for companies to be able to easily remove filters (with out going into the data base).
Reality is: People leave companies. Developers leave projects. They do not clean up their own messes. I have 2 saved filter working on very old versions (3 years ago) and I can't remove it from the main page.
Check how appear the main page http://jira.nhibernate.org/secure/Dashboard.jspa  (actual version is NH2.0.0).
What mean "Administrator" if he can't administer ? A mitigate way between delete a filter and remove it from main page can be : FilterSharedLevel FilterSharedLevel : Personal | Group | Global The admin can't remove the filter created by a user but he can change the FilterSharedLevel. This is not a minor inconvenience, but I see it was first reported in 2006. It is now 2008. We've only been using Jira for a few months. We've already got everyone's screens cluttered up with 5 filters written by an employee who has left the company. Please bump this up in priority.
Would be great to be able to do it. I can't help someone right now because I don't have any possibility.
It would be nice to have a way to at least delete all the subscriptions for a disabled user.
Here's the scenario that we came across.
Some user's have lots of subscriptions and it is a bit tedious to go and delete them all. Alternatively, we could change the user's email address to use a fake address, but the mail server would still try and send these. This has become an issue for our company too and I see no reason, technical or otherwise, why administrators should not be able to modify, delete or remove sharing of global filters. Let's get some more votes for this item!
I opend a support case and requested an escalation. Maybe there is a product manager who can take this on.
Vote is set Greta's comment is our feeling exactly.
Additionally we would like to be able to unshare a filter without deleting it. Even if you log in as the user you cannot (directly do this)! Is there a workaround for this? We need a way of updating a filter for a user that has left. To add to the challenge their login has been removed from Active Directory so its difficult impersonate their login.
Please fix this, the backdoor no longer works!
If 160 admins think this is needed. Then either you fix the damn thing or you wait a little longer 'till everybody switches to another app. It's not a good policy to make admin's mad. If 160 companies paying a license fee is not enough money then I don't think paypal will do it. I guess they only do stuff for enterprise and not prof. So 1 needs to upgrade to enterprise and get this fixed.
Or wait another 2 years and hope this #@# bug gets fixed I think we must take it easy...
I ""solve"" it removing the SavedFilters-Portlet from the DashBoard... at the end all pre-defined issue-filters are pretty enough. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Improvement
Open
Major
Allow administrators to manage filters owned by other users
I have updated the summary to make this issue (hopefully) easier to find.
I can see how this would be useful, but please note that we have a lot of feature requests. The way we schedule new features is described here:
http://confluence.atlassian.com/display/DEV/Implementation+of+New+Features+and+Improvements
Is the main porblem that you have filters left over from deleted users?
Thanks,
Anton