Value Field Condition from JSUTIL doesn't work with Calculated Number Field from JMCF plugin?

Hi,

I have a calculated number field (provided by JMCF plugin, https://marketplace.atlassian.com/plugins/com.innovalog.jmcf.jira-misc-custom-fields) which calculates some properties of the issue, and I want to have a workflow condition (provided by JSUTIL plugin, https://marketplace.atlassian.com/plugins/com.googlecode.jira-suite-utilities), based on this field, i.e. "The field <fieldname> will have to be less than value '0'. Compared as Number."
When I set this condition, the workflow transition becomes unavailable in all issues, even in the issues that comply to this condition (JQL search "<fieldname> < 0" returns them).
I tried various conditions with this field, and the only one that works (transition becomes available) is "The field <fieldname> will have to be equal to value 'NULL'. Compared as Number." It seems that the JSUTIL retrieves the Calculated Number Field's value as NULL.

Is my conclusion correct, or am I missing something?
Regards,

Laura

1 answer

1 accepted

You should ask that question to the JSUTIL team. Maybe they don't support Calculated Fields (which is a standard JIRA feature).

I did label the question with both plugins as I didn't know which end was the problem, but after hundredth rechecking I found that the problem was actually on my end - there was a mistake in the calculated fields code, and JSUTIL was more "correct" in retrieving the field value. Probably I should delete the question altogether, as it is no longer a question, but maybe someone runs into a similar problem, so I will leave it with an explanation (sorry for not using terms like "namespaces", but I know too little about how the actual calculations happen :)): I missed a variable declaration in the field's formula. If it was the only calculated field, it would have been returning null (and maybe throwing errors in jira log, not sure about that). But variable with the same name is used in other calculated fields, so all views, screens, searches etc. did show a value for the calculated field in question, and only JSUTIL managed to somehow process it "in isolation", and (correctly) evaluate it to null.

Suggest an answer

Log in or Sign up to answer
Atlassian Community Anniversary

Happy Anniversary, Atlassian Community!

This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.

Read more
Community showcase
Bridget Sauer
Published yesterday in Marketplace Apps

Calling all developers––You're invited to Atlas Camp 2018

 Atlas Camp   is our developer event which will take place in Barcelona, Spain  from the 6th -7th of   September . This is a great opportunity to meet other developers and get n...

38 views 0 3
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you