...
Custom field to screen relation
Screen A screen is detected as a dependency if the custom field is added to and shown on the screen.
...
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
Filter 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
Dashboard 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.