JQL - expression or IssueFunction in expression

[MelvinDave]

Hi,

I would like to know why my JQL query does not work even though I put the right variables: 

issueFunction in expression('', 'Preestimate=Estimation')

Both fields have numerical values. 

[Peter-Dave Sheehan]

I would highly recommend you enter a sub-query to make sure you don't attempt to evaluate this for all of your issues.

But I think you will need to use a double-equal:

issueFunction in expression('', 'Preestimate==Estimation')

[MelvinDave]

Hi Peter. I did that but it did not work. 

[Trudy Claspill]

Hello @MelvinDave 

I also found this information in the documentation:

Custom field names are likely to have spaces, which can’t be parsed. If so, remove the spaces. It’s not case-sensitive but use camel-case for maximum readability. If your field names have any other punctuation you must use the format customfield_12345.

Are you sure you have the correct field names?

You can only use custom fields that have a configured searcher, as, for performance reasons, we only retrieve values from the Lucene index. The standard searchers are supported, searchers supplied by plugins will not work.

Have you configured your custom fields with a searcher?

[MelvinDave]

Hey. Yes, I am sure I am using the correct field name, but do I need to use the field instead of the name?

[Trudy Claspill]

I'm not clear where that screen image you provided comes from, but I believe you need to be using the field name (without spaces) as it appears in the Custom Fields screen. 

I suspect in this case you would be needing to use "PreliminaryEstimate(SP)".

I think you also need to be using the double equals for the comparison, as @Peter-Dave Sheehan mentioned.