Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

The operator '=' is not supported by the 'Budget ID' field.

Howard Nedd
Contributor
September 2, 2021

I have a custom field "Budget ID"  (type is: number field).

I have the following Budget ID which is filled in in  an issue: 2002132

I am using the JQL: 

"Budget ID" = 2002132

and I am getting the following error:

The operator '=' is not supported by the 'Budget ID' field.

I have also tried to use: "Budget ID" ~ 2002132

I receive the same error.

Tried JQL:
"Budget ID" is 2002132

Same error.

Is there something I am missing here?

2 answers

1 accepted

0 votes
Answer accepted
Howard Nedd
Contributor
September 2, 2021

Solution found:

 

Resolution:

You would just need to replace the "Budget id" to "cf[17800]" which is the Jira default on the filter query . By doing this you'll be able to query again your results.

At the moment, JIRA allows creating any new custom field with any name, including creating duplicated fields. However, we have a feature request open to prevent duplicate field creation here: Prevent duplicate field creation

Jack Brickey
Community Champion
September 2, 2021

Yep. When you start typing a CF the auto-complete offers the correct field. You don’t need to know the cf[] info specifically.

0 votes
Jack Brickey
Community Champion
September 2, 2021

Hmmm…can you share your exact JQL here?

Howard Nedd
Contributor
September 2, 2021

Solution found:

Cause:

This is duplicated because a user with administration power from our  instance created it.

So, to not  mess with the instance to delete the duplicated field you can adjust your filter to use the field ID instead of the field name, which is safer than using the name.

Resolution:

You would just need to replace the "Budget id" to "cf[17800]" which is the Jira default on the filter query . By doing this you'll be able to query again your results.

At the moment, JIRA allows creating any new custom field with any name, including creating duplicated fields. However, we have a feature request open to prevent duplicate field creation here: Prevent duplicate field creation

Suggest an answer

Log in or Sign up to answer