Managing custom fields in Jira effectively

[Malayamaan]

To Improve of JIRA Instance performance - We are planning to use our instance Custom fields more effectively as per the suggestion from Atlassain from document  : https://confluence.atlassian.com/enterprise/managing-custom-fields-in-jira-effectively-945523781.html?_ga=2.232157727.1452201035.1598123940-480285568.1562077941

As per the Strategies mentioned - Kindly clarify the below for our understanding

1. Delete any unused custom fields

Question :

1. As per the plugin "Custom Field Toolbox for Jira"  - it showing the Custom fields extract values and the fields and project used for the Custom fields - If unused Custom fields are deleted  - Is there will be any impact?

2. Impact on the existing workflows or the configurations for the Unused Custom Fields removed?

Limit the scope of the custom fields to specific projects context - In our Instance most of the Custom fields are context selected as "Global Projects" - if we need to change the context from  Global to Single Project (Used by Custom Field) - What is the right procedure to it and it will be any impact for limiting to a single or More Projects?

[[ANS] Alexey Dorofeyev]

Hi Malayamaan,

Question :

1. As per the plugin "Custom Field Toolbox for Jira"  - it showing the Custom fields extract values and the fields and project used for the Custom fields - If unused Custom fields are deleted  - Is there will be any impact?

2. Impact on the existing workflows or the configurations for the Unused Custom Fields removed?

Since Jira provides a very wide range of customization options, we cannot 100% guarantee that there are no impact on deleting custom field. The data provided by our application is accurate and we are constantly working to expand this data. Our backlog contains tasks, for example, of defining the use of fields in the issue security schemes, permission schemes and compatibility with third-party applications such as Jira Workflow Toolbox, Script Runner, SIL engine, etc. In addition, it is not always possible to detect the use of the field. For example, if you develop your own app and its code contains a reference to a field, we cannot detect this. Therefore, before deleting the field, make sure that you have made a backup.

Limit the scope of the custom fields to specific projects context - In our Instance most of the Custom fields are context selected as "Global Projects" - if we need to change the context from  Global to Single Project (Used by Custom Field) - What is the right procedure to it and it will be any impact for limiting to a single or More Projects?

There is nothing unusual about the procedure. Just identify all projects that use a given custom field and change the context from global to project-specific, and apply the custom field only to relevant projects (by adding these projects to the local context.)