How does Power Admin for Jira detect the custom field usage?

This document explains how Power Admin evaluates and finds the usage (the dependent configuration elements) of the custom fields in a Jira instance.

Usage in projects and issues

Custom field to project relation

The app finds and shows the projects where the custom field is configured.

Custom field to issue relation

The app finds all the issues which have values for the custom field.

Usage in screens

Custom field to screen relation

A screen is detected as a dependency if the custom field is added to and shown on the screen.

Usage in workflows

Custom field to workflow relation

Workflow is detected as a dependency if there is a reference to the custom field in one of the properties of a workflow participant.

Usage in schemes

Custom field to issue security schemes relation

Issue security scheme is tracked as a dependency if the custom field is added as a value of at least one of the fields User custom field value and Group custom field value in an issue security level that is part of this scheme.

Custom field to notification schemes relation

Permission scheme is tracked as a dependency if the custom field is added as a value of at least one of the fields' User custom field value' and 'Group custom field value' in a notification that is part of an event in the scheme.

Custom field to permission schemes relation

A Permission scheme is counted as a dependency if a particular permission is granted to the User custom field or Group custom field and is part of the permission scheme.

Usage in Agile boards, filters, and dashboards

Power Admin finds all the agile boards, filters, and dashboards using the custom field. We go through all the JQL queries in agile boards and filters and look for references to the custom field.

Custom field to Agile boards relation

An Agile board is shown as a dependency to the custom field in the case where:

There is a reference to the custom field in the board's JQL entries (Saved filter, Cardcolors, Quick filters, Subqueries, Swimlanes).
The custom field is configured and shown in the board's backlog or in the active sprints in the board's card layout.
The custom field is selected in the Estimation Statistic field of this Agile board for statistical purposes.
The custom field is added as a field shown in the detail view of this Agile board.

Custom field to filters relation

A filter is shown as a dependency to the custom field if its JQL query refers to the custom field.

Custom field to dashboards relation

A dashboard is shown as a dependency of the custom field if the dashboard gadget has a property of custom field type, and its value is the name or id of the field.

Usage in Service projects

Dependency is detected when the custom field is referred to in Request types, Queues, SLAs, or (Legacy) Automation rules. Usage detection happens when the Service Projects' Cached Index is generated for the first time or when it’s refreshed.