Automation-Sum of Remaining estimation

[Lilit Tsaturyan]

Hello Jira Automation Community,

I've created a new Custom Field called "Initial Remaining."

My objective is to set up an automation that operates as follows:

Whenever a sprint starts or there's a change in the sprint field value, the automation should trigger. Its task is to copy the current Remaining Estimate value into the Initial Remaining field.

The Remaining Estimate should be calculated based on the sum of remaining estimations from all sub-tasks. 

Note: I have no value on Parent's Original/Remaining Estimation fields. 

Despite my efforts to implement this automation, it seems to be encountering issues.

Would anyone in the community be able to provide insights or suggestions for resolving this matter?

Thank you for your assistance.

[Kalyan Sattaluri · Accepted solution]

Hello @Lilit Tsaturyan 

Welcome to the community.

Regarding your rule:

Your current trigger, "Sprint Value Changed" is not the right trigger you want for your requirement. Because the way you have it, rule will fire when a Sprint value is changed on a story/issue. Thats not what you said you wanted. Your rule trigger should be "Sprint Started". So thats one to use. 

Once you change your trigger, you dont need those JQL If conditions, instead you need to choose "Branch" Component, choose JQL as an option in the drop down and give your JQL there. That is, your JQL should just say, issuetype = Story. You dont need OpenSprints() clause in JQL because thats the trigger and its implicit. 

Then, Once inside the branch, you can edit the issue they way you have it..

Please make these changes and try, share screenshots of rule/audit log if issues. Hope it helps, Thanks!

[Lilit Tsaturyan]

@Kalyan Sattaluri  
Thank you for your response, 

To clarify further, I'm looking to set up 2 automations:

1. The first automation should triggered by "Sprint Started"

2. The second automation should be triggered when an issue is added to a sprint, utilizing the "Sprint value changed" trigger.

I have attached a screenshot containing the automation used for the second case. Please review it at your convenience.

[Kalyan Sattaluri]

OK. If you are trying to implement your rule #2, then your rule set up seems right... We need to confirm if you subtasks "remaining estimate" field is giving results or not.. if its not, there may be syntax issue or we may have reference it by its customfield value...

To test that, Can you, before you edit the issue:

• Add log statement to log {{issue.subtasks.remaining estimate}}
• Run this rule by adding an issue to an active sprint and share the audit log.

To add a log statement, choose Add Component -> New Action -> Type "Log" in search box and choose "Log Action".. see screenshot below..

[Lilit Tsaturyan]

Thank you. 
You can check screenshot below:

[Kalyan Sattaluri]

Hello @Lilit Tsaturyan 

Sorry for coming back so late.

Please share your Edit issue syntax as well. Looks like you may have an issue with syntax.. Share screenshot and copy paste aswell.,

[tatevikalaverdyan]

Here is the Edit action- 

{
"fields": {
"Initial Remaining": "{{#=}}{{issue.subtasks.Remaining Estimate}} / 3600{{/}}"
}
}

[Kalyan Sattaluri]

Hello,

Try below syntax,

Please share audit log if errors..

{
"fields": {
"Initial Remaining": "{{#=}}{{issue.subtasks.Remaining Estimate.sum}} / 3600{{/}}"
}
}

Thanks,

Kalyan

[tatevikalaverdyan]

Thankss @Kalyan Sattaluri  it worked

[Kalyan Sattaluri]

Great, @Lilit Tsaturyan please review as well and consider accepting solution so it benefits others in future. Thanks!!

[Lilit Tsaturyan]

@Kalyan Sattaluri 

Accepted.
Thank you for your support. 

[tatevikalaverdyan]

I have the same issue. @Kalyan Sattaluri  can you review the reply?