Issue Summary

Loading the "add subscription" modal on filter details takes several seconds, and the UI is temporarily frozen when the tenant has a large number of groups.

Steps to Reproduce

1. Use a tenant with a high number of groups (original CS ticket had 91k)
2. Go to a filter
3. Click on the "filter details" link next to the filter name
4. Click on the "Add subscription" button

Expected Results

Load "Add subscription" modal normally, and UI is not laggy

Actual Results

"Add subscription" modal takes a couple of seconds to load, and interacting with the Recipients dropdown is laggy

Workaround

Cleanup unused groups in the tenant.

Modal still works even though it's slow

Effectively clean up unused groups in the tenant by following the steps below.

Step 1:

• Use the Jira Cloud REST API to:
• Retrieve all groups.
• For each group, fetch its members.
• Identify groups with zero users.

• The relevant endpoints are:
• `/rest/api/3/groups/picker` — Get all groups.
• `/rest/api/3/group/member?groupname= {groupName}

  ` — Get users in a group.

• You will need to script this process (using Python, bash, etc.) to automate checking each group for members.

Step -2
Before removing any groups, please ensure that they are not referenced anywhere in your Jira instance. Even groups with no members might still be used in:

• Permission schemes
• Notification schemes
• Issue security levels
• Shared filters and dashboards
• Automation rules

Currently, Jira Cloud does not provide a single place to view all group references, so this review needs to be done manually.

Helpful Tool:
To make this process easier, you might consider using the Lens Group Debugger for Jira plugin. This tool can help you:

• Identify where groups are used across your Jira projects
• Clean up group references more efficiently