|
History
| Log In
|
|
|
|
Is the problem that they are shared filters cluttering the filters portlet? Why else would the number of filters be an issue?
Excessive filters clutter the portlet and the manage filters screen. They also would (in my educated guess/opinion) contribute to slowing down the entire server. On the manage filters screen, there is an "issues" count column. The only way to get that number is to actual filter all the issues in the database for each filter in order to get the count. If you have many... even hundreds of filters, that means it has to search the database many or hundreds of times each time that screen is loaded. With 50,000 + issues, that can take some time. That screen in our JIRA install takes about 5 seconds to load today.
I like this suggestion, but would like to offer a revision. Instead of allowing administrators to delete a filter, at least allow them to unshare it. Or alter the shared groups... That way the original creator does not lose the filter. Yes, the number of filters cluttering up the List ALL Filters portlet. Also, a user at the time not so familiar with JIRA created way more filters than really necessary (some of the preset filters would do), and now that individual is gone and no way to clean things up. At first this wasn't such a big and so I didn't jump on this when I should have, alas. Now other projects have popped up and more filters added by various folks. So now it's really apparent that we need to clean things up, but as far as I can see there's no way?! I guess I'll have to fudge something with some of these old accounts so that I can clear out some of these old filters, but there really needs to be some sort of admin interface to edit or change the ownership of filters as needs change.....
if the user has left the company, you can reset their password, log on as them and delete the filters as needed. but this is a very crude way of doing this and really should be part of an admin feature.
In our situation, we had a user create a filter that is used by many people. This filter needs to be updated regularly. Since the user left the company, we can neither update nor remove the filter.
Another way to manage the problem of dealing with filters whose authors have left the company would be to allow project administrators to reassign the filter to another user, or take authorship of it themselves.
I agree with all of the comments so far - there should be a way to manage these filters and hacking the password is not ideal.
I just ran into the same problem: I do have to delete the filters for over 20 users by hand (changing password, logging in, deleting the filter, deactivting user again). THIS IS RIDICULOUS and I honestly and deeply hate Atlassian for forcing me to do so. I plan to get an discount for the next purchase we make in exchange for my working time. As great as Atlassian products are, sometimes you stumble upon very basic features that are missing.
This is becoming a real administrative burden for us. Please allow Admins to unshare filters.
Hello everybody. I've put the vote counter to 55.
If these votes are consolidated with JRA-9997 than we have 143. Oops, 144 because I still have to vote for the second one |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
|
Improvement
Open
Major
Administrators should be able to delete all filters
.
Thanks,
Jason