Original Estimate: smart value doesn't work if time is less than 1 hour

Question

Hello every one

I built an automation to update a field related to the original estimate.

But when i fill original estimate by 30m(or any data less than 1h), jira switch it by 0.5h.

That's ok but the automation doesn't seem to understand as i wish because, the result is 0 and i expect 4.

This is my automation smart value

* {{#=}} {{ issue.fields.timetracking.originalEstimateSeconds.divide(3600).mutiply(8) }}

It works with an original estimate greater than 1.

Can you help me please ?

DS_48fkhh · Answer

Thank you Bill.

I find another solution which works.

On a confluence page, i add a "jira filter/issue" macro inside a "table transformer" macro.

Then with an SQL query, i'm able to convert "original estimate" as integer and multiply it.

Than you for your time

Best Regards

Jordan

Bill Sheboy · Answer

I am using Jira Cloud, not Data Center, and so I wonder if there is a difference in behavior with the units of measure.

Where in your rule are you seeing the Original Estimate as I do not see that?

Also, your rule appears to edit a field and then write to the audit log.  When a rule runs, the actions are based on the issue values at the time the rule started.  It does not automatically update those in-memory values, even though you have updated the Jira database with the rule actions.

Please try adding a Re-fetch Issue action after your edit and before the write to the audit log:

https://confluence.atlassian.com/automation/jira-automation-actions-993924834.html#Jiraautomationactions-refetchissuedataRe-fetchissuedata

DS_48fkhh · Answer

Thank you Bill and sorry for my mistakes.

I have edited my post with images.

No i don't includ units, i set the field value to a "number field" from which its name is enough, i don't need it.

i also see, jira return round values.

for exemple, if originalEstimate = 1h2m, result expected is 8.48 but it's 8.