Jira project configuration clean-up and performance tuning

Purpose

Large Jira instances often contain hundreds or thousands of custom fields, workflows, screens, and other types of Jira configuration elements. Jira's flexible nature accommodates the need to tailor the configuration of the system based on the unique processes and operational needs of any business. However, this level of flexibility causes a tremendous diversity among data dimensions, and each data dimension can influence Jira's speed.

Two significant factors impact the speed of any Jira instance:

• The increasing number of issues.

• The increasing number of custom fields and other configuration elements.

The first factor is handled by the Configuration Manager's archive use case, which enables you to regularly archive old issues, thus tuning the performance of your Jira instance.

The second major factor — an increased number of custom fields and other configuration elements — is handled by Power Admin for Jira and its capabilities for conducting performance tuning and effective, error-free cleanup.

Well, Power Admin for Jira allows you to perform:

• Performance tuning - the ability to identify duplicate or similar configuration elements (e.g., custom fields) and reuse them instead of creating new ones.

• Clean-up - the ability to quickly and easily identify unused or rarely used configuration elements and delete them.

Configuration Analysis & Clean-up

Assessment of Jira project configurations 

“As an administrator, when I get a request to add a new configuration element, like a custom field or workflow, I want to be able to find out all elements of the same type to evaluate whether I can reuse an existing element instead of creating a new one.”

Large Jira instances comprise thousands of configuration elements that keep piling up with each new user change request. Over time, the increase in new configuration elements (e.g., custom fields) negatively impacts the speed of the Jira instance.

The Power Admin for Jira app allows you to quickly identify duplicate or similar configuration elements and reuse them instead of creating new ones. The tool's powerful search features enable you to review the usage of configuration elements, such as workflows, custom fields, etc., at a glance.

After you trigger the search action, you see a results page listing the configuration elements with their names, IDs, and projects where this element is used as part of the project configuration.

Open

Jira project configuration clean-up

“As a Jira administrator, I want to be able to analyze exactly where and how the configuration elements are used and remove the ones that are unused or rarely used.”

Power Admin for Jira gives you the ability to quickly and easily search for and analyze the usage of various configuration elements across the entire system. Its powerful filter mechanisms allow you to refine your search results further and find configuration elements in complex use cases or identify problems in your Jira configuration. This is accomplished by using the following advanced and sophisticated filters:

• Projects - the most common filter, visible in all searches; filter the configuration elements by the projects in which they are used

• Type - filter custom fields by configuration type

• Global Context - enable/disable global context as a filter for custom fields

• Lead - filter projects by their assigned lead users

• Category - filter projects by category

Open

These filters allow you to refine your search or display only the unused configuration elements. For example, if you want to discover the unused custom fields in any given project, you can easily refine your search criteria by clicking on the Projects filter and then on the None tab. The filter name will change from Projects to Not Used in Projects, and Power Admin will find and list all objects not used in any project.