Jira automation; Issue Accessing Original Estimate Value on Initial Set

[Allan Conybeare]

I have an automation that triggers on field change for time tracking on create issue and edit issue, see screenshot. 

I'm trapping that a field has changed with -

if any match using -

{{fieldChange.field}} equals timetracking

or

{{fieldChange.field}} equals timeoriginalestimate

Which is working well and traps a change but my logic fails the first time the original estimate field is set, it's not on the create screen, when I try to get the new original estimate I'm using the value in "issue.timetracking.originalEstimateSeconds" but it is returning empty (when it's first set) even though I know it has a value, on further edits it has the correct value and works perfectly, so just might not be the most reliable one to use. Interestingly the value is actually set when you look at the issue just not accessible in the value when the automation is run which means my rule does not complete correctly.

I've been trying to figure out what other fields might have this value but not had much joy -

• fieldchanged.to
• fieldchanged.toString
• changelog.timeoriginalestimate.to

The above are also empty on the first edit

It's highly likely that I'm doing something foolish. I've attached a screenshot of the rule showing the part of the rule where I think the issue is.

I'd also like to figure out how to get varHours to default to 0 (zero) when Original Estimate is empty, but I've asked that in a separate question. (solved)

Any help will be greatly appreciated :) 

Edited: added a revised image that shows assigning the variable varHours that defaults to 0 if the estimate is empty. Thanks Bill Sheboy 

[Allan Conybeare]

This is a filthy solution but I've got it to work by having a second trigger on issue create that sets the Original Estimate to 0m.