Use Custom Field Name vs. Custom Field ID

Question

I have a Custom Field Name I want to use:

"Story Points[Number]" is EMPTY ORDER BY created DESC

But is does not return the desired results.

Using Field ID does work, but is not desired:

cf[10012] is EMPTY ORDER BY created DESC

Why am I unable to use the field name?

Daniel Ebers · Answer

Hi @Matthew Risch

I recall some Suggestions and Bugs from jira.atlassian.com, something like this one:
https://jira.atlassian.com/browse/JRACLOUD-76536

In your opening post you are referring to field "Story Points" but later you are referring to several spellings of "team" in fields - I don't know if this was just an example?

For the similar bug reports the solution was indeed to use the ID as well.

There is also a report around where "EMPTY" does not return the desired result if the field was previously populated.
https://jira.atlassian.com/browse/JRACLOUD-74027
https://jira.atlassian.com/browse/JRACLOUD-74809
Probably this does not apply here, unless one of the "Team" fields is of type multi-line (Text Field).

Cheers,
Daniel

Matthew Risch · Answer

I know that if there are various custom fields with the same name, it will then require the ID to Differentiate, so perhaps that something.  Currently there is:

Team

Team.

TEAM

in the system for one field I am looking to see if is empty, but these should be different enough for Jira to not be confused. NOTE: I’m aware there is some reorganization needed given this example of the Team field isn’t unique in this environment, but that is a different topic and is underway)

A buddy of mine suggested that maybe there is a Nextgen project within this instance that has the Team field, which would cause this one to need the ID.   I’ll look into that and respond back.

appreciate the help!!

Matthew Risch · Answer

Agreed - Every instance I've ever used has allowed both the Custom Field Name or the Custom Field ID to work when querying to see if the field is EMPTY.  Except this one.