| Table of Contents |
|---|
...
🎯 Purpose
Optimizer for Jira (DC/Server) contains a feature for optimizing custom fields.
Custom fields with global contexts are available to use by all projects in your Jira instance, but only a handful actually use them. To improve performance, you can automatically change their context to project-specific, applying them only to relevant projects.
Overview
Optimizer for Jira provides a four step process of automatically identifying and configuring optimal scope for Custom Fields.
1. Scan for Fields
You can configure what criteria are used to identify Custom Fields for optimization by specifying a maximum number of allocated Projects and Issue Types, and minimum number of Issues. This can be configured in the Advanced section, shown in the figure below.
...
2. Select Fields
Optimizer will display Custom Fields that match the specified criteria and display a preview of Suggested Scope for each field, as shown in the figure below.
Use the checkboxes in the table to select custom fields for optimization and click on the Select Fields button to confirm your selection.
...
3. Preview Changes
Once the selection of custom fields has been confirmed, you can preview the New Scope for each custom fields before any changes have been applied, as show in the figure below.
If you are happy with all changes, click on the Apply Changes button.
...
4. Optimized Fields
Optimizer for Jira will display the changes that have been applied, as shown in the figure below.
...
a global context (i.e., custom fields that can be used in every project and issue type) may result in poorer performance when there are many of them within a Jira instance. In most cases, these global-context custom fields are only used by few projects and issue types. Thus, the optimize custom fields feature localizes the global context of these custom fields to just the projects and issue types where they are used.
Custom field optimization is context-preserving; existing custom field configurations other than the global configuration are considered when performing an optimization.
...
🚶♀️ Walkthrough
There are 4 phases in the custom field optimization process, as detailed below:
Step 1 – Scan for Fields
In this phase, you are provided with high-level information that outlines the process for optimizing custom fields.
You are then instructed to scan the instance to identify optimizable custom fields. There are also advanced options available where you can adjust the criteria for identifying candidate custom fields. These criteria include:
Associated minimum number of issues.
Associated maximum number of projects.
Associated maximum number of issue types.
...
During this process, you are also presented with the option to expand the search to include archived projects, which we recommend occasionally to help maintain data integrity.
...
Step 2 – Select Fields
After scanning for custom fields, Optimizer will display all the custom fields with a global scope that match the specified criteria (in the advanced options). You can then select one or more custom fields you wish to optimize.
| Info |
|---|
Optimizer will only progress with selected custom fields that are unlocked. |
When a custom field row is selected, the suggested scope of the custom field is given. This suggested scope is the list of projects and issue types relevant to the custom field, minus any projects that already feature in configurations other than its global configuration. If there are already configurations covering all projects, then the resulting optimized context will be empty.
...
Step 3 – Preview Changes
After selecting which custom fields to optimize, you are then given the opportunity to review and confirm the changes before the optimization process begins.
...
Step 4 – Optimized Fields
When you are satisfied with the changes that will be made during optimization, then the ‘Apply Changes’ button can be selected and the final confirmation screen displayed.
The confirmation screen displays the status of the optimization tasks performed (as they are performed). As well as a status indicator for each custom field, a ‘View’ link is provided which will open a new tab to the corresponding custom field’s configuration page. This allows you to review and confirm any configuration changes made by Optimizer.
...
Additionally, when a custom field’s global configuration is emptied by the optimization process, Optimizer will leave a note within the description of this custom field explaining why this has happened. This feature improves accountability for unorthodox changes within the Jira instance, especially if this empty context is retained (its removal is recommended) and the custom field’s configuration is viewed by a user that did not carry out the optimization.
...