Hey everyone
im using automation to sum up the original estimate (I'm using Jira's structured field) for stories to a custom field. The problem is when I enter an estimation that is not an integer (for example 1.5 hours) it rounds down the number in the custom field to 1 hour.
How can I prevent the rounding?
Thank you
For a question like this, please post images of your complete rule, showing the details of any calculations in the edits, and of the audit log showing the details of the execution. That will provide context for the community to suggest ideas.
Until we see that...I suspect you either have a missing or incorrect unit of measure for the time units at the place the math is occurring.
Kind regards,
Bill
Hey Bill,
Thank you for your answer. This is my complete rule:
I'm trying to sum up the subtasks' original estimate to a custom field "Updated Estimate" in the parent stories.
When I enter a rounded hour for example 2 hours it works fine and I get the number 2, but when I enter for example 30mins it rounds to 0, 1.5 hours is rounded to 1.
Thank you
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
What is the type of your Updated Estimate field?
If you write that smart value expression (used in the edit) to the audit log, what do you see as the value: the rounded one, the unrounded, or something else?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
What exactly do you mean?
This is an image of the audit log when I changed the Original Estimate of the subtask to 30mins. I'm not sure I understood you correctly
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.
What I believe is happening is because Original Estimate is an integer (number of whole seconds), that type is being used for the rest of the expression.
To break that typing-chain and use a non-integer, try a math expression, such as this:
{{#=}}{{issue.subtasks.Original estimate.sum}} / 3600{{/}}
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.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.