Automation do not fill Original Estimate

[Martin Herold]

Hi all, I spent quite some time on this issue and need to result to ask the community to confirm my observation or help me with the solution. I have already search the community topics but found none that would help my situation.

I am trying to configure an automation to fill the original estimate based on the Story Points. Why? Because the team that I started to work with is using Story Points but I need to be able to observe the time (JIRA reports, planning, etc.) based on the estimates in time, time spent and remaining estimate. I don't want to disrupt the team method if it is works for them and just wanna calculate the original estimate based on historical data. What I found out is that for the team 1 Story Point = 10 hours. The project is company managed and the estimation on the board is configured to Story Points with Time Tracking enabled.

My issue is with the automation and filling the field. My original attempt with the action "Edit work item fields" was that the Original Estimate was filled by smart value with the calculation inside of it. This action works and if you look at the Story then it successfully fill the Original Estimate field. However this seems to be only visual and when logging the time there is no remaining estimate in the pop-up window and JIRA behaves like the original estimate is not filled at all. I have tried to change the edit action using JSON to fill directly the time tracking object originalEstimateSeconds. With that the automation ends up with success but not value is changed which seems like the internal API silently rejects the request. The same I tried to fill both original and remaining estimate with JSON but with the same result.

The automation trigger is working without an issue, the calculation is working and when logging the value before filling then it is correct.

Is there a way to fill the Original Estimate field from the automation to actually fill the Original Estimate value which would then behave like I would fill it manually or is there a persisting bug in the automation? 


JSON example for time tracking:

{
"fields": {
"timetracking": {
"originalEstimateSeconds": {{#=}}{{issue.Story Points}} * 36000{{/}},
"remainingEstimateSeconds": {{#=}}{{issue.Story Points}} * 36000{{/}}
}
}
}

[Robert DaSilva]

Hi @Martin Herold , welcome to the Community!

I'd like to restate your challenge to ensure I have a good understanding.

• You are working in a Jira Space that is primarily using Story Points to estimate work effort
• You need to be able to tie an amount of time to each story point, and this has been deemed 1 point = 10 hours
• You need to update all the historical work items to add an Original Estimate value, and use this for reports
• You have set up an automation rule that can correctly populate the Original Estimate value
• You have set up an automation rule that can correctly populate the Remaining Estimate value

And you're running into the following challenge

• With the work items where automation have populated the Original and Remaining estimate, you're finding that the Time Tracking dialogue box is not reacting how you would expect.
• You expect the time tracking box to show you how many hours were in the original estimate, as well as count down as time logs in the remaining estimate field.

Could you confirm I have this right?

---

The only thing that comes to mind immediately is you may want to put a "s" at the end of your input calculation. This will result in the entry being a string, something like 108,000s.

I might suggest also simplifying your math to simply multiple the story points by 10, then putting an "h" at the end to indicate hours. I would populate this for both Original and Remaining estimate.

Robert