Add the Original Estimate to an automation

[Milagrosa Puig]

I tried to add the original estimate to the tasks I want to create automatically in Jira:

What I do:
Then --> Create a new -- task:

I go to the configuration section: "Choose fields to set"...and add "Original Estimate". I go to that field and add, for example, 2h. I click on update and Run Rule to test the automation:

and when I go to see the created task, it creates it, with its title, description and so on, but it does NOT add the original estimate of 2h, instead, 0m appears:

That I have to do?
Thank you!!

[Bill Sheboy]

Hi @Milagrosa Puig 

For a question like this, please post an image of your complete automation rule, images of any relevant actions / conditions / branches, an image of the audit log details showing the rule execution, and explain what is not working as expected.  Those will provide context for the community to offer ideas.  Thanks!

Kind regards,
Bill

[Milagrosa Puig]

Oh sure! Thanks for answering me and telling me that, I'm going to update my message :) 

[Bill Sheboy]

Thanks for the screen images.

In your rule's Create Issue action, you have selected the Original Estimate field from the drop-down list and tried to set the field with advanced edit with JSON.  If you review the audit log details when trying to run the rule you should see an error.

Only one of those edit  types can be done at a time, so please try removing one of them and re-test.

[Milagrosa Puig]

Hi Bill! Thanks for answering.
I deleted the code that I wrote in the field with advanced edit with JSON, and filled in only the Original Estimate field, and nothing, it still doesn't work for me :( I get the original estimate at 0m when I launch the rule.

[Nic Brough -Adaptavist-]

I think you may need to be setting the estimate fields as a number of seconds (as that is how they are stored in the database).  4h is the "pretty" format of 14400 seconds, which I don't think Automation understands.

[Bill Sheboy]

Okay, after some testing I confirmed something (that I recall learning before for automation rules but seem to have forgotten)...

Issue creation is separate from time tracking / logging work, and so the issue must be created first and then time tracking (like original estimate) can be set.  The REST API functions appear to support doing them at the same time, however there appears to be something different for rules use of those functions.

@Milagrosa Puig for your scenario, are the Original Estimates the same or different for each new Task?

If they are the same, your rule could do this:

• trigger: scheduled
• action: create task (without the time tracking set)
• action: create task (without the time tracking set)
• ...
• branch: to All Created Issues
  • action: edit, to set the Original Estimate, using the drop down field and entering what you need, such as with 4h  (The human-friendly time value does work, Nic.)

If each Original Estimate is different, the rule structure is different:

• trigger: scheduled
• action: create task (without the time tracking set)
• branch: to Most Recently Created Issue
  • action: edit, to set the Original Estimate, using the drop down field and your estimate
• action: create task (without the time tracking set)
• branch: to Most Recently Created Issue
  • action: edit, to set the Original Estimate, using the drop down field and your estimate
• ...

[Milagrosa Puig]

ohhh yes! You are SUPER TOP!
That's the way to do it!

I have used the second option because I have several tasks in the same schedule.

Thank you very much! :) :) :) :) :) :) :) 

[Alyssia Grant]

I would also love to know how to get this working if there is anyone to answer this that would be greatly appreciated!