Comparing Two Custom Fields

Question

I have a custom jira type called Objective that has two custom fields:

* Target Value - represents the target metric of the Objective (e.g., 100, 1, 5, etc). Any numeric value above 1.
* Current Value - represents the current metric of the objective, Any numeric value from 0 to less than or equal to Target Value.

I'm new to the jira admin side of the house and have been investigating ways to enforce that Current Value is less than the Target Value. I've tried automation setups, smart fields, etc. and without using ScriptRunner (Groovy).  I haven't had luck getting this complete.  What suggestions do you have to address this?

Kurt Huhner · Answer

Updated rule: I've added the action to move the work item to LOGGED on success:

Rule with Action to move to LOGGED:

Audit Log: Shows "No Actions Performed"

I simply do not want users to create tickets with Current Value >= to Target Value. Unless I am in the wrong area or missing something this seems to be a straight forward method...but I'm missing a trick somewhere.

Bill Sheboy · Answer

Hi @Kurt Huhner

First thing: for the rule you show, that will always try to transition the work item back to the same status it is currently in (i.e., a looping transition).  Is that what you wanted?

Next, what are the types of those fields: number, select-option, etc.?

Next, I personally recommend never using the new-ish feature to add conditions directly to triggers.

* There is too much risk of the known racetrack timing problems with some triggers causing unpredictable results
* Instead, try using separate conditions after the trigger
* And, for cases with a Work Item Created trigger, add a Re-fetch Work Item Data action after the trigger, but before the conditions

Finally, after any changes and re-testing, please post images of the updated complete rule and the audit log details showing a rule execution.

Kurt Huhner · Answer

Bill,

I have got what I believed was the right syntax for your suggested approach, but the rule doesn't stop "invalid" values.  Can you review this and see if I'm missing something silly?

I tested and entered 5 for Current Value and 2 for Target Value which should have caused a rejection, but the jira was created.

Rule Trigger:

Condition:

Flow: