How does Power Admin for Jira track the filter usage?

This document explains how Power Admin identifies the usage and dependencies of filters in a Jira instance.

Shares and subscriptions

As part of the usage report, Power Admin for Jira detects the subscriptions and shares of a filter:

• Number of shares of a filter - filters can be shared with other users via user groups, projects, and project roles. Power Admin detects the number of users or other objects in Jira with which the filter is shared. Read more about sharing a filter in Jira.

• Number of subscriptions to this filter - users in Jira can subscribe to the filter by email and receive updates when there are changes to a filter. Power Admin tracks the number of subscriptions to a filter. Read more about filter subscriptions in Jira.

Agile boards, dashboards, and filters

To collect all the data about a filter's usage, Power Admin detects all the agile boards, dashboards, and filters where it is in use. It goes through their JQL entries and looks for references to the filter.

Filter to agile board relation

An agile board is detected as a dependency if:

• The filter itself is the saved filter of an agile board.

• There are references to the filter in JQL queries in an agile board (Saved filter, Cardcolors, Quick filters, Subqueries, Swimlanes).

Filter to dashboard relation

A dashboard is detected as a dependency if the filter name or ID is present as a property in the dashboard gadget.

Filter to filter relation

A filter is detected as a dependency when the filter name or ID is present as a reference in another filter's JQL entry.