Automation rule to be generated to sum up the Original estimate & Logged Hours in Parent(EPIC)

Revathy
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
April 24, 2024

Hi All,

I created an automation rule to sum up all the Original Estimates and Logged work of all linked issues under epic level..I wanted to add all the estimates and logged hours of Story,Improvement,Sub task,tasks to be populated under the Time tracking in Epic level..Whenever hours are logged or estimates has been updated it should sum and add those values under the Epic.

I referred this page and followed the steps but its always throwing Lookup Issue error and Unknown operator issue.I will also attach the screenshot of the rule & error .


Referred Linkhttps://community.atlassian.com/t5/Automation-questions/How-to-use-automation-to-sum-up-in-EPIC-the-hours-logged-in/qaq-p/1954914

image.pngimage.png
Kindly help me in finding the solution.

Thanks in Advance!

Revathy Madhavan

1 answer

0 votes
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.
April 24, 2024

Hi @Revathy -- Welcome to the Atlassian Community!

In your rule, your log action uses {{issue... but it should use the {{lookupIssues... smart value.  Regardless of that problem...

Unfortunately, the Lookup Issues action for Jira Data Center version does not support most fields yet, including the time tracking ones: https://jira.atlassian.com/browse/JIRAAUTOSERVER-877

If it is of any consolation, when Lookup Issues was first added for Jira Cloud, it also only had about a dozen fields, and a year later all of the others were added.  So I recommend watching that suggestion to see any progress.

 

For your scenario, the workaround is to call the REST API issue search with the Send Web Request action, using the same JQL as your original Lookup Issues call.  Then all fields should be available for the sum. 

If you want to try that approach, here is a how-to article for calling a REST API function from a rule and the function I believe is needed:

https://community.atlassian.com/t5/Jira-Software-articles/Automation-for-Jira-Send-web-request-using-Jira-REST-API/ba-p/1443828

https://docs.atlassian.com/software/jira/docs/api/REST/9.13.0/#api/2/search-search

Kind regards,
Bill

Revathy
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
April 24, 2024

Hi @Bill Sheboy ,

Thank you for the update, Let me try & check with REST API option.

But meanwhile i would like to know if there is any possibility using scripts in ScriptRunner Behaviours/Scripted fields  to achieve the expected solution.
If possible kindly attach the script or any reference link ..

Regards,

Revathy Madhavan

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.
April 25, 2024

I believe that is possible, although I am not a ScriptRunner or Behaviors user and so cannot confirm that.  Perhaps check their docs or wait for another community member who uses the product to post ideas.

Suggest an answer

Log in or Sign up to answer