How do I automatically update the parent story's Original Estimate in Jira Lite?

[Sarah Jones]

I am using Jira Lite (now cloud?) and would like to have all estimates from subtasks roll up to Stories and Epics, however I am having issues with the automation setup. 

The steps I have are:

1. Navigate to Automation Rules: Go to your project's Project settings > Automation or System > Automation rules in Jira settings.
2. Create a New Rule: Click Create rule.
3. Add a Trigger:
   • Select the "Field value changed" trigger.
   • Configure it to trigger when the "Original estimate" field changes.
   • Ensure the trigger applies only to relevant issue types, typically Sub-task.
4. Add a Condition (Optional but Recommended):
   • Add a "Condition" component and select "Issue condition".
   • Set the condition to Issue Type is Sub-task to ensure the rule only runs for sub-tasks.
5. Add a Branch:
   • Add a "Branch rule / related issues" component.
   • Select "Parent" as the related issue type (or "Epic" if the parent is an Epic). This action allows the rule to access and modify the parent story.
6. Add an Action:
   • Within the branch, add an "Edit issue" action.
   • Select the "Original estimate" field.
   • Use a Jira smart value to sum the estimates from all sub-tasks. The smart value should look like this: {{issue. subtasks. original estimate. sum}}.
7. Save the Rule: Name your rule and click "Turn on" to activate it. 

However I see no trigger for "Original Estimate" listed. Any help would be appreciated. I've attached a photo of the automation system I have incase that helps. 

[Bill Sheboy]

Hi @Sarah Jones 

First, it appears you are using a bot-generated suggestion for the rule.  I recommend caution when doing so as such tools cannot access your Jira site configuration, and thus the "guesses" may be less relevant or accurate.  Even the Atlassian-built bot has trouble guessing many scenarios for the same reasons.

Instead, I recommend reviewing the Atlassian-provided documentation and template examples to help you get started with the rule:

https://www.atlassian.com/software/jira/guides/automation/overview#what-is-automation

Next, you want to update the parent work item when the Original Estimate changes.  There is no trigger specifically for most fields:

https://support.atlassian.com/cloud-automation/docs/jira-automation-triggers/

Instead, there is a Field Value Changed trigger, and you may use the generic option to detect any "Time tracking" changes in the field Fields to monitor for changes.

Next, the bot guess for the subtask Original Estimate is incorrect.  Instead please try this one:

{{issue.subtasks.timetracking.originalEstimateSeconds.sum|0}}

To learn smart values such as this which are might not be listed in the documentation, please use this how-to article:

https://support.atlassian.com/cloud-automation/docs/find-the-smart-value-for-a-field/

Finally, you note wanting to sum the values for subtasks to parent work item, and then from those to the Epics.  That will require a second rule as the types and smart values are different.  I recommend starting with the subtask summing rule first, then add the other one.

Kind regards,
Bill

[Sarah Jones]

Hi

Thank you and yes this was the "help" bot Rovo within Jira lite itself. which wasn't helpful at all. 

I find the full/standard Jira a lot easier to deal with but sadly only have access to the Lite version at work. 

Appreciate the help

[Bill Sheboy]

@Sarah Jones are you using Jira Cloud, Server, or Data Center?

With Cloud, there is only one "version" of automation...although there are additional features at the highest license levels of Premium and Enterprise.