The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Automation - Issue fields condition: Does not accept decimal value

Simon Tilbury
Contributor
May 19, 2023

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

 

Screenshot 2023-05-19 115958.png

 

 

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

1 vote
Dan Breyen
Community Champion
May 19, 2023

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.

Simon Tilbury
Contributor
May 22, 2023

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 

TAGS
AUG Leaders

Atlassian Community Events