Original Estimate and Remaining Estimate Sum up to parent , issue created and work effort updated

Dominic Roy Arokiaraj October 16, 2024

The issues are created by CSV import.

Screenshot 2024-10-16 at 5.59.48 PM.png

An automation rule should trigger to sum up all the original estimate and remaining estimate of the child issues to the parent 

Now the original estimate and remaining estimate of subtask should be updated to Story which inturn update Epic.


When work effort is logged to the subtask, an automation rule should trigger to calculated the remaining estimate update the subtask , story and Epic.

How to create the automation rule?

1 answer

0 votes
Marc - Devoteam
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.
October 16, 2024

Hi @Dominic Roy Arokiaraj 

Even if we built this automation, it won't trigger as automation rules don't trigger on CSV import.

If you want this on the issue, make sure there is a field for this in Jira and set that field as a column in your CSV, with the calculated value.

Than you have in on the issue.

If we should create an automation rule to do this, then this would only trigger when you update an issue in Jira or change a field value in Jira.

Dominic Roy Arokiaraj October 16, 2024

In Automation Trigger there is a option "Issue Created" . I hope this will trigger the Automation rule.

There is a field called Original Estimate and Time Remaining. I have given it in the CSV screenshot

Marc - Devoteam
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.
October 16, 2024

Hi @Dominic Roy Arokiaraj 

Not on creating issues via CSV import, only if you create issues via the GUI or API

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.
October 16, 2024

Hi @Dominic Roy Arokiaraj 

Yes, and...to the suggestions from @Marc - Devoteam 

There are many posts in the community for a similar scenario.  I recommend searching the posts to find example rules as a starting point, try to build your rule, and then ask for help if it does not work as expected. 

Successfully using automation rules requires learning and experimentation.  When one just uses rules created by others without understanding them, they will be unable to maintain them.

Kind regards,
Bill

Dominic Roy Arokiaraj October 16, 2024

Thanks for the input @Bill Sheboy  I have gone through many article here regarding this and I have created rule to update the sum. I didn't get a clear answer whether it possible through automation.

One level updation is happening. From subtask to story but not story to Epic. More over with the given CSV screenshot, the time remaining is not updating and remains 0. 

When I create manually , whatever estimate I gave in Original estimate will get updated in the time remaining field. But while importing the issues its not updating the time remaining field. Its shows 0. I think its because of the below warning Screenshot 2024-10-17 at 10.50.47 AM.png

 

Please do suggest a way around to accomplish 

Marc - Devoteam
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.
October 17, 2024

HI @Dominic Roy Arokiaraj 

As I explained.

Import via CSV doesn't trigger automation rules. It creates issues with the information provided in the CSV.

That's all what will happen.

If you then create an automation rule to execute a math function, this will only trigger when you make a change on an issue in Jira

Dominic Roy Arokiaraj October 17, 2024

Thanks @Marc - Devoteam for your inputs. Will look into it 

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.
October 17, 2024

Import with a CSV file does fire the event and can trigger a rule with Issue Created

I hypothesize the challenge for your scenario is some data is updated after the issue is created (which is the same thing as when this happens in the UX).  You will need to experiment to confirm if the issue history shows multiple events when importing those fields.

Dominic Roy Arokiaraj October 22, 2024

Sure @Bill Sheboy Will give it a try on your scenario and will let you know on the result

Like Bill Sheboy likes this

Suggest an answer

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

Atlassian Community Events