Help needed with automation for Original Estimate Field in JIRA

Vishal Gogari
Contributor
March 2, 2025

Hi Team,

I have a automation in place such that when a new issue type = story is created, 6 sub-tasks are created via automation for that specific story. 

Now when the user adds original estimate value for the first time then the value for original estimate in the parent story reflects correctly. Below is the automation rule for my project:screencapture-tataaig-atlassian-net-jira-software-c-projects-PLCTR-settings-automate-2025-03-02-23_01_08.png

Problem comes when the estimate is revised for any of the sub-tasks. The revised estimate doesn't get updated in the sub-task as well as parent story.

For the first time everything works fine but when any of the sub-task estimate is revised things go for a toss. How can I prevent the same? Please help.

1 answer

1 vote
Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
March 2, 2025

Hi @Vishal Gogari 

First, when posting automation rule questions, please also include images of the relevant actions (e.g., Edit Issue Fields) and of the audit log details showing the rule execution (with all of the areas at the right side arrows > expanded for execution).

 

Next, you state this:

Problem comes when the estimate is revised for any of the sub-tasks. The revised estimate doesn't get updated in the sub-task as well as parent story.

Are you describing when a person changes the time tracking field Original Estimate in the Sub-task that field does not change in the Sub-task?  As written, your rule is only trying to update the parent issue of the Sub-task.  Please clarify what you believe to be the problem.

 

Kind regards,
Bill

Vishal Gogari
Contributor
March 2, 2025

Yes you are correct, when the person changes the original estimate in subtask it's doesn't update in sub-task nor in the parent story.

Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
March 2, 2025

I recommend first disabling the rule and investigating why the value is not storing in the Sub-task.  Once that is corrected, you may return to working on the rule.

Perhaps start with the issue history in the Sub-task to learn if something is clearing the field after it is set.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events