How does Power Admin for Jira track the filter usage?

This page will reveal to you document explains how Power Admin evaluates and finds identifies the usage (the dependent configuration elements) of the 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:

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

• Count Number of subscriptions to this filter - Users 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 the filter it is in use. We go It goes through the their JQL entries in agile boards and filters and look and looks for references to a the filter.

Filter to

...

agile board relation

Agile An agile board is detected as a dependency in the following casesif:

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

• If there There are references to the filter in JQL queries in an Agile board like a saved agile board (Saved filter, card colors, quick filter, subquery, or swimlanes Cardcolors, Quick filters, Subqueries, Swimlanes).

Filter to dashboard relation

A dashboard is detected as a dependency if the filter name or id 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.

...