Why do I suddenly see a duplicate custom field with JQL, but is not in Custom Fields?

[Darrell Rangel]

cf[1007] is the original custom field. Yesterday, I just noticed cf[10143] as an option (which has no results if I filter for it). When I search in Custom Fields, there is only one Region entry. Now when I create a chart using Region, it returns "irrelevant", and I believe bug is the reason.

[John Funk · Accepted solution]

Hi Darrell,

I suspect at least one of those was created in a Next-gen project. Those projects don't have a concept of sharing already created custom fields. So you could create the same named custom field across multiple Next-gen projects. 

Do a query like Region is not empty and see which projects come up. 

[Darrell Rangel]

Yup - that was it! I renamed the field in the Next-gen project and it's resolved.

Thank you, John!

[John Funk]

Great! Glad I could help 🙂

[Matt Doar]

Authenticate as an admin, then go to rest/api/2/field

Search in your browser for Region. I would you to find two custom fields

Look for the Admin, Audit Log page using g g

Search for Region

Alternatively, edit any custom field

change the cf id in the URL to that of the second field 10143 and reload

Now you are editing the second Region field and can add a prefix to it such as " 2"

See who complains

[Matt Doar]

All this if you're not using Jira Cloud :)