Can I Delete Filters in JIRA 3.13?

[Bradley Kyer]

We are currently running JIRA Enterprise Edition, Version: 3.13-#330 and I was wondering if there is a way for me (I am the Administrator) to delete Filters for employees who no longer work here? If the Filter is Shared then I am able to see it, but I do not see a way to delete it.

Also, what happens to the Private filters for those users? Currently our policy is to NOT delete the user when they leave, just remove the jira_user permission so they can not access the app. Crazy, I know, but hey, that's not my call.

We are in the planning stage to upgrade to the latest JIRA version and I see it has the Delete Filter ability, but if I could delete them now and not have to bother migrating them, then that would be great.

[J. Caldwell · Accepted solution]

All the docs he has are here:

https://studio.plugins.atlassian.com/wiki/display/JSU/JIRA+SU+%28Switch+User%29+Plugin

It basically functions like a Linux sudo, where you assume the identity of the user if you have the required permissions (administrator). For me it is useful for:

1) Attempting to replicate an issue with out changing things from a end user perspective

2) The ability to fix things that phone/web conference isn't and then show them exactly what I am talking about in relation to their items

3) Fix things broken by those who have left

Even of you are using a SSO solution, the user should still exist in Confluence in some way. You would be assuming that users identity ONLY in Confluence. It reads the permissions of the person who is logged in (e.g. You) and if you have the required permission level, it will allow you to get in once you click on the "SU" link next to the user.

[J. Caldwell]

All the docs he has are here:

https://studio.plugins.atlassian.com/wiki/display/JSU/JIRA+SU+%28Switch+User%29+Plugin

It basically functions like a Linux sudo, where you assume the identity of the user if you have the required permissions (administrator). For me it is useful for:

1) Attempting to replicate an issue with out changing things from a end user perspective

2) The ability to fix things that phone/web conference isn't and then show them exactly what I am talking about in relation to their items

3) Fix things broken by those who have left

Even of you are using a SSO solution, the user should still exist in Confluence in some way. You would be assuming that users identity ONLY in Confluence. It reads the permissions of the person who is logged in (e.g. You) and if you have the required permission level, it will allow you to get in once you click on the "SU" link next to the user.

[Bradley Kyer]

Thanks J.

Is there documentation on its usage? I can not see any links to it. If not, no biggie, I get the drift on what it is trying to do, but I just wanted more information to justify to management. My main question is how does it log-in as the other user? We do not set a password on the Create User screen, but instead we use our Novell login credentials to log into JIRA - so the same credentials are used for all our systems.
Thanks,
Brad.

[J. Caldwell]

https://plugins.atlassian.com/plugin/details/5043

It is pure genius

[Bradley Kyer]

Thanks you for your answers. What is the "SU Plugin"? I do not see it at plugins.atlassian.com/plugin.

[J. Caldwell]

I second Jo-Anne's process and I cannot speak highly enough about the SU plugin. It is core to allowing us to troubleshot problems.

[Jo-Anne MacLeod]

The SU plugin will allow you to log in as that user, and unshare it, and then delete it. Or you can simply reset their password to something that you know, and then log in as that user. Unfortunately that is the only ways available in 3.13.

Oh, if you choose to go with the SU plugin, makes sure that you choose the version of the plugin that is designed for your version of JIRA.