Hi everyone, we've also wanted a way to find whether or not a group is present in a filter's view/edit permissions or JQL text – regardless of who owns the filter.

When you're considering renaming a group, it's especially useful to pull up a list of related filters. We created a Jira cloud app that allows you to drill into a specific group and list filters that are related to it via view/edit permissions and/or JQL text.

The Jira cloud app is called Lens Group Debugger for Jira, and you can check it out here: https://marketplace.atlassian.com/1236381

Try the app out, and let us know what you think. Thanks!

+1 vote

A more user-friendly alternative to the current workaround would be amazing!

Hello,

I followed the workaround described above, I removed all the filters tha use the name of the Group I want to change, but I keep getting the "We're unable to edit the group name XXX, as it is used in Jira administration settings. To edit this group name, first remove the group from the following Jira settings: JQL Filters - Result".

I am at my wits' end. Is it possible that the above error message is also raised if a filter mentions a User that belongs to the Group whose name I want to change, and not just the Group's name?

Thank you all for your support.

EDIT: I found out the cause of the problem. The output of  "YOUR_SITE_NAME.atlassian.net/rest/api/3/filter/search?expand=jql&overrideSharePermissions=true" is paginated. There are 350 filters in my Jira instance. A simple call like the ne above only retrieves the first 50. I had to write a Scriptrunner script to retrieve all filters' pages and find the ones to be disabled before renaming the Group.

Hey!

Thank you for raising this request. From my point of view:

• If you intend to restrict the changing of the group name because of existing JQL filters, please display which filters include this group name in the query.

• I tried to change the group name from Labcon to LABCON, but encountered an error stating "existing group with that name". The error message was not clear, but after some trial and error, I realized that it meant there is already a group with the same name. I first changed it to "Labcon 1" and then tried to change it back to "Labcon". This issue also needs to be addressed. For this part, I suggest changing the error message to something that indicates that the existing group also refers to a group written in the same way (including lower/upper case letters).
  For example: “existing group with that name (including lower/upper case letters)”