Custom Fields

On this page:

Custom fields and their usage

Custom fields are one of the building blocks of a Jira configuration. As you might end up with too many custom fields on your system or too many duplicates, you need a fast-track to find and manage your custom fields in Jira. Power Admin for Jira allows you to find any custom field and get full report about its dependent workflows, schemes, screens, agile boards, dashboards and filters.

You can view where and understand how each custom field is used. Power Admin also shows all the projects where the custom field is configured and all the issues that have values for the custom field.

Find custom fields

To find a custom field:

  1. On Power Admin's Landing page, select Custom Field from the drop-down, type a name or ID, and start your search.

  2. On the Search results page, click on the name of a custom field. You can filter further the custom fields by usage in projects, their type and global context (use the Projects, Type or Global Context filter next to the search field). Learn more about the additional filters you can use on custom fields.

  3. Then, the custom field’s profile page appears.

Search results

The page with search results shows the following information for each custom field:

  • Name, type, and id of the custom field - You can search for a custom field by its name or ID.

  • Projects - count of the projects where a custom field is configured. When you click on the project count lozenge, you could view a list of all the projects.

Custom field's profile page

Using the profile page, you could view all the details about a custom field and its usage.

How does Power Admin track the custom field usage?

Power Admin finds all projects where the custom field is present in the project configuration. The usage information also includes the issues that have values for this custom field.

Power Admin collects all the screens, workflows, issue security schemes, notification schemes, permission schemesagile boards, filters and dashboards that use the custom field. We go through the JQL entries of agile boards, filters and dashboards and look for references to the custom field.

Learn more details about how Power Admin tracks the usage information of custom fields.

Usage Information

A custom field’s usage information is presented in the Summary and Details sections on its profile page.


The Summary section shows:

  • Count of the projects where the custom field is configured. You can click on the count to view list of the projects.

  • Count of the issues that have values for the custom field. When you click on the issue count, you will be redirected to the Issue Navigator listing the issues.

  • Count of dependent screens, workflows, issue security schemes, notification schemes, permission schemes, agile boards, filters and dashboards.


The Details section of the profile page shows details about permissions, global permission, issue security schemes, events, workflows, agile boards, and filters that use the custom field. You can then navigate if you want to, to the profile pages of issue security schemes, workflows, and filters.

Agile boards and dashboards do not have profile pages in Power Admin.


The following actions are available for custom fields:

  • Rename - You can click on the name of a custom field to rename it. Rename is a safe activity which means that the name of the custom field will be updated in all dependent configuration elements referring to it by name.

  • Configure - redirects you to the custom field’s configuration page in Jira.

  • Edit - redirects you to the custom field’s edit page in Jira.

  • Delete - deletes the custom field and shows warnings if it is currently in use.

  • Export - exports a custom fields usage information in CVS.


Using Locations feature, you could find detailed information regarding where and how the custom fields on your Jira instance are used in agile boards, filters, dashboards, workflows, permissions, and events.

Locations of custom field usage in screens, issue security, notification and permission schemes are not available.