Summary:
Jira Cloud administrators currently lack a centralized way to view where user groups are referenced across the instance. This limitation makes it difficult to efficiently manage permissions, conduct audits, support business restructuring, and ensure compliance—especially in large or complex environments. A single, unified report or dashboard that displays all group usages (including boards, filters, workflows, dashboards, global permissions, and swimlane filters) would significantly improve administrative efficiency, reduce risk, and support critical business processes.

Description:
As a Jira Cloud administrator, it is critical for business operations, compliance, and efficient user management to have visibility into where user groups are referenced and utilized across the instance. This includes—but is not limited to—roles such as board administrators, filter subscriptions, workflow conditions, dashboard sharing, global permissions, and swimlane filters.

Business Need:
Currently, tracking group usage requires manual checks across multiple areas, which is time-consuming, error-prone, and not scalable for large organizations. Admins often need this information for restructuring, audits, compliance, and user access reviews. In some high-priority use cases—such as maintaining board admin groups—there is absolutely no alternative to manual review, which can take many hours and introduces risk of oversight.

Technical Limitations:
Existing REST API endpoints (e.g., /rest/api/3/dashboard) only return results for dashboards to which the querying user or app has explicit access. This means automated scripts (such as those run via ScriptRunner Add-On User) cannot comprehensively enumerate all dashboards or their sharing settings, resulting in incomplete data and 404 errors for inaccessible dashboards. This technical barrier further reinforces the need for a native, centralized reporting solution within Jira Cloud.

Requested Solution:
A centralized location or report within Jira Cloud where administrators can view all references and usages of a specific group across the entire instance. This should include:

• Boards (admin roles)

• Filters (subscriptions and sharing)

• Workflows (conditions, post-functions)

• Dashboards (sharing)

• Global permissions

• Swimlane filters (JQL/group references)

• Any other relevant configuration areas

Benefits:

• Saves significant admin time and effort, especially for high-priority group management use cases where manual checks are currently the only option

• Reduces risk of missed permissions or access

• Improves audit readiness and compliance

• Supports business restructuring and user lifecycle management

• Addresses technical limitations of current API/app-based solutions, ensuring admins have complete and accurate visibility