How to reliably identify Agile custom fields when they are duplicated due to the upgrade bug

[Sergey Gussak]

A JIRA Server instance can have duplicated Agile fields due to this bug: https://confluence.atlassian.com/jirakb/duplicate-agile-software-custom-fields-after-upgrading-jira-software-779159142.html

In that case, relying on the field schema in not enough. For instance, there will be multiple com.pyxis.greenhopper.jira:gh-sprint fields. Is there a way to tell through JIRA API which field is actually used by JIRA Agile?

I understand that there is a procedure to remove the redundant filed, but I'm asking about the situation when this is not an option.

[Ismael Jimoh]

Hi @Sergey Gussak 

The easiest way to find if you have duplicated fields would still be the database.

Run the query on the page up till before the OR condition  in the Where statement.

This should normally pull all JIRA software type field for you. 
You can then compare the names to see the duplicates.

As for finding which fields are used, you can only do this by creating an issue and potentially running a Jira Rest api call for tge said issue to pull all details for said issue. This should show you the correct custom field id for issues.

• You can also right click and inspect elements in your browser from the view issue page in Jira.

Hopefully this helps a bit.