You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
I am trying to create an automation that sends an email if one field is miscalculated. Custom Field 6 should be equal to 250 * Custom Field 2.
I have an advanced compare condition that says
First value: {{issue.customfield_6}}
Condition: does not equal.
Second value: {{#=}}{{issue.customfield_2}} * 250{{/}}
I have an issue where
Custom Field 6 = 1250
Custom Field 2 = 5
I'm still getting the email. I tried reversing the condition to "equals" and still got the email.
What am I doing wrong here?
Hello @Melissa Kibrick
In your Automation Rule have you made use of the Log action to print out the value of Custom Field 6, Custom Field 2, and your math operation to ensure they have the values you expect?
Are your two custom fields Number type fields?
Yes, and...to Trudy's answer: if you post images of your complete rule and the audit log details showing the rule execution those may help identify the cause, and exclude any causes from the rule structure/organization. Thanks!
Kind regards,
Bill
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Trudy Claspill Thank you! I didn't know about the log action. The values are coming is as 1250.0 and 1250.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Sounds like the advanced compare is a text compare, and not a numeric one! And one of those values is not dropping unnecessary zero value, decimals digits.
So a couple of work-arounds are...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thankfully, I was able to use the "less than" compare to get what I needed.
Thank you @Bill Sheboy for a more elegant solution.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Melissa, will the "less than" always work if the values are reversed in magnitude?
If not, you can enforce the comparison order with the absolute value operator, abs, added to the end of that expression.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.