I want original estimate to sumup in Product story
Asked by Tehmina Aslam:

Hi,

I have a custom issue type hierarchy: -

Epic - Product Story - Technical Task - Subtasks

We estimate Technical Tasks in hours using the "original estimate" field. I want to create a rule that:

1. Checks if all the Technical Tasks have original estimates.
2. Sums up all the original estimates and places the total in the original estimate field of the Product Story.

Here is the smart value I am using: \`\`\` {{#=}}{{issue."technical task".remaining estimate.sum}} / 60{{/}} \`\`\`

Thank you for your assistance. Best regards, \[Your Name\]

{{#=}}{{issue."Technical Task".remaining estimate.sum}} / 60{{/}}


Answers:
author: Bill Sheboy
body: Hi [@Tehmina Aslam](/t5/user/viewprofilepage/user-id/4670711)

For a question like this, please post an image of your complete automation rule, images of any relevant actions / conditions / branches, an image of the audit log details showing the rule execution, and explain what is not working as expected. Those will provide context for the community to offer ideas. Thanks!

Until we see those...

You describe an issue hierarchy of:

* Epic
  * Product Story
    * Technical Task
      * Subtask

And so your issues likely use the built-in *parent* field to link together.

The expression you show will not work, as "Technical Task" is not a field / smart value: it is an issue type.

Instead you would need to gather the Technical Task issues for their parent (a Product Story) and then sum the values. To do this, you could use the Lookup Issues action and then reference the smart values for time tracking.

Here are some references to help do that:

<https://support.atlassian.com/cloud-automation/docs/jira-automation-actions/#Lookup-issues>

<https://support.atlassian.com/cloud-automation/docs/jira-smart-values-issues/#--issue.timetracking-->

Kind regards,  
Bill

comments: author: Tehmina Aslam
body: You want to sumup to all on technical tasks and then from tech to product story. right? because I want on product story

There you go...

![2024-06-15_13h31_53.png](https://community.atlassian.com/t5/image/serverpage/image-id/330059i732D9019E25EB9B3/image-size/large?v=v2&px=999 "2024-06-15_13h31_53.png")


author: Bill Sheboy
body: Please post images of the audit log details showing the rule execution and of the Edit Issue action.

You described wanting to sum the values in the Technical Task issues which are children of the Product Story issue...

* The JQL condition seem incorrect as that will not test if the trigger issue is a Technical Task
* And, as described earlier: to do what you ask you will need to use the Lookup Issues action to gather the Technical Task issues related to the trigger issue

If this is unclear, please discuss your rule with your Jira Site Admin for support.


author: Tehmina Aslam
body: let me tell you more details ... i rename epic as a product story and the technical task is actually a standard issue type (i.e story)

1) here I just want to collect all the original estimates value in the technical tasks under a product story, and just sum up in the original estimate field of the product story...

and the sum of the time spent in subtasks to technical tasks and from all technical tasks to product stories under one epic. (maybe in the custom field)

Here are the logs...

![2024-06-20_11h50_51.png](https://community.atlassian.com/t5/image/serverpage/image-id/330750iA55BA54E10C386D0/image-size/large?v=v2&px=999 "2024-06-20_11h50_51.png")


author: Tehmina Aslam
body: Okay, i have updated a few things, but it is still not working for me...

Let me clear, my issue types are renamed as

Epic = Product Story \&

Story = Technical tasks

![Screenshot 2024-06-24 131739.png](https://community.atlassian.com/t5/image/serverpage/image-id/331334i12BA15F8232F9253/image-size/large?v=v2&px=999 "Screenshot 2024-06-24 131739.png")![Screenshot 2024-06-24 131907.png](https://community.atlassian.com/t5/image/serverpage/image-id/331336iCC5669025F0343E9/image-size/large?v=v2&px=999 "Screenshot 2024-06-24 131907.png")![Screenshot 2024-06-24 131918.png](https://community.atlassian.com/t5/image/serverpage/image-id/331335i9E393E760762B5D9/image-size/large?v=v2&px=999 "Screenshot 2024-06-24 131918.png")![Screenshot 2024-06-24 131925.png](https://community.atlassian.com/t5/image/serverpage/image-id/331337iE3F48BEC5421C44D/image-size/large?v=v2&px=999 "Screenshot 2024-06-24 131925.png")![Screenshot 2024-06-24 131948.png](https://community.atlassian.com/t5/image/serverpage/image-id/331339iB004E66F477A7D9C/image-size/large?v=v2&px=999 "Screenshot 2024-06-24 131948.png")![Screenshot 2024-06-24 132021.png](https://community.atlassian.com/t5/image/serverpage/image-id/331338i5B9D322DEEEEDB83/image-size/large?v=v2&px=999 "Screenshot 2024-06-24 132021.png")![Screenshot 2024-06-24 132050.png](https://community.atlassian.com/t5/image/serverpage/image-id/331340iC581FE83A7876198/image-size/large?v=v2&px=999 "Screenshot 2024-06-24 132050.png")


Tags: cloud

jira-cloud