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.
Am trying to write an automation rule that will be triggered if a number field is above 2.5. However automation does not accept decimal values
Simon, I'm unable to recreate that behavior. If I create a number field, in Automation it will allow me to use a decimal field. Have you looked at how that field is defined? (Settings / Issues / Fields / Custom Fields) I'm wondering if there's something unique to that field definition that only allows whole numbers.
Tried with a new field and same issue. Not much you can do on field config for such a field. Tried setting default value but this made no difference. This is a company managed project if that makes any difference and no changes to field configuration. Hmmm
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.