Is there a way to know which custom fields are used in which projects from Custom Fields Page?

[Milan Chheda [INFOSYSTA]]

As JIRA Administrators, we have access to Custom Fields page wherein we can create new custom fields. Once the field is created, we associate them to screens. And screen schemes are then associated to Projects.

Is there a way to know, from the Custom Field page just like screens or workflows, as to which custom fields are getting used in which projects?

Objective: 

We want to rename & delete certain custom fields but before doing that, we would like to know this custom fields are used in which all projects.

Thanks,
Milan

[Tom Lister · Accepted solution]

Hi @Milan Chheda [INFOSYSTA]

Take a look at this post of mine using SQL to answer a similar question.

https://community.atlassian.com/t5/Jira-questions/Is-there-a-way-to-see-all-connected-issue-types-to-custom-field/qaq-p/947655

There is no quick way to get this info from the Jira pages.

[Milan Chheda [INFOSYSTA]]

Thanks Tom, but I don't have access to database. 

Is there an alternative? Or any add-on?

[Tom Lister]

Hi Milan

This looks useful

https://marketplace.atlassian.com/apps/1216607/custom-field-manager-for-jira?hosting=server&tab=overview

I’ve not tried it. There may others on the Atlassian Marketplace 

[Milan Chheda [INFOSYSTA]]

This looks like a helpful add-on. Thanks Tom!

[Vishnukumar Vasudevan]

Alternatively, you may have a look at the list of screens this field is added and get the list of projects use those screens. May not be 100% accurate but still it helps.

[Milan Chheda [INFOSYSTA]]

Thanks @Vishnukumar Vasudevan, but that would be completely manual, cumbersome and error-prone. Also, the number of projects in JIRA are lot, and hence there are many screens too. Doing it manually, is probably the last resort but definitely requires lots of effort, of going thru each screen manually. 

[Vishnukumar Vasudevan]

Yes, it is. But can be consider if you are not supposed to install any third party add-ons in your instances and agree that it's error-prone.