Have a field for multiple tasks in one epic roll up to a field in an epic
Asked by Mona Aghamirsalim:

![jwm 4.JPG](/t5/image/serverpage/image-id/257877iF5126DCDC328AB27/image-size/large?v=v2&px=999 "jwm 4.JPG")![jwm 3.JPG](/t5/image/serverpage/image-id/257878i56CB3C1CD7BABD63/image-size/large?v=v2&px=999 "jwm 3.JPG")![jwm 2.JPG](/t5/image/serverpage/image-id/257879i4EB2BB53741EC6B0/image-size/large?v=v2&px=999 "jwm 2.JPG")![jwm 1.JPG](/t5/image/serverpage/image-id/257880iA8247CF841474391/image-size/large?v=v2&px=999 "jwm 1.JPG")

Imagine each Epic and Task (that is a child of the Epic) have a field called JWM Story Points. How can I have the JWM Story Points field of the epic, show the sum of the JWM Story Points of all its children. {{issue.children.JWM Story Points.sum}}, {{issue.child.JWM Story Points.sum}} and {{issue.tasks.JWM Story Points.sum}} and {{issue.task.JWM Story Points.sum}} have not worked so far. I do know that this idea will work for subtasks -{{issue.subtasks.JWM Story Points.sum}}- for a friend of mine but I have tasks that roll up to an epic not subtasks rolling up to a task.


Answers:
author: Trudy Claspill
body: Hello [@Mona Aghamirsalim](/t5/user/viewprofilepage/user-id/5216460)

You need to use a Lookup Issue action within in your For branch to lookup the child issues of the Epic.

![Screen Shot 2023-05-18 at 8.28.43 AM.png](https://community.atlassian.com/t5/image/serverpage/image-id/258100i152C4C946B833E6E/image-size/large?v=v2&px=999 "Screen Shot 2023-05-18 at 8.28.43 AM.png")

You'll have to change the field name from "Story Points" to the name you use for your field.

comments: author: Mona Aghamirsalim
body: I am not sure why this is not working for me. your response Looks very promising though and I hope you don't give up on me :) . I did whatever you said except instead of story points I have JWM Story Points and instead of Story, I have task. Maybe if it is task I should use something other than {{issue.key}}? ![jwm 3.JPG](https://community.atlassian.com/t5/image/serverpage/image-id/258531i23295776E5189BF5/image-size/large?v=v2&px=999 "jwm 3.JPG")![jwm 2.JPG](https://community.atlassian.com/t5/image/serverpage/image-id/258533i51E0D51D096C2EED/image-size/large?v=v2&px=999 "jwm 2.JPG")![jwm 1.JPG](https://community.atlassian.com/t5/image/serverpage/image-id/258532i0EE13C5688017934/image-size/large?v=v2&px=999 "jwm 1.JPG")


author: Trudy Claspill
body: I apologize. I missed an error in your rule.

The For branch has selected the wrong item. "For Parent" is to find the parent issue only for subtask type issues.

When you want to find the parent Epic you need to use "For Epic (parent)":

![Screen Shot 2023-05-21 at 9.32.37 PM.png](https://community.atlassian.com/t5/image/serverpage/image-id/258549i260598F5A9EAD2AC/image-size/large?v=v2&px=999 "Screen Shot 2023-05-21 at 9.32.37 PM.png")


author: Mona Aghamirsalim
body: ![jwm 1.JPG](https://community.atlassian.com/t5/image/serverpage/image-id/258693iBCFAAD5A718642E3/image-size/large?v=v2&px=999 "jwm 1.JPG")![jwm 2.JPG](https://community.atlassian.com/t5/image/serverpage/image-id/258694iE8CADEB3D53F2C7F/image-size/large?v=v2&px=999 "jwm 2.JPG")![jwm 3.JPG](https://community.atlassian.com/t5/image/serverpage/image-id/258696iB81986A5B5E77EF3/image-size/large?v=v2&px=999 "jwm 3.JPG")![jwm 4.JPG](https://community.atlassian.com/t5/image/serverpage/image-id/258695iF243CD4A3DE728D5/image-size/large?v=v2&px=999 "jwm 4.JPG")

I feel you are soooo close to solving this issue :) . The numbers still don't roll up. The trigger is any change to JWM Story Points. when I trigger the task level JWM story points to populate, the automation runs for the tasks successfully (look at log) and it runs for the parent as well but the JWM story Points for the parent (epic) is not populated. So odd since something must be happening to the JWM story points field of the Epic (parent) or why would the automation get triggered for the epic even if it is take no action?


author: Trudy Claspill
body: I have just now noticed that you are working in a Team Managed project (looking at the bottom left corner of the very first image in your original post).

Team Managed projects don't use the "Epic Link" field. Instead they use the "Parent" field.

In the Lookup Issues action in your **For Epic (parent)** branch, change **"Epic Link"** to **"Parent"** in the JQL.


author: Mona Aghamirsalim
body: MAGIC! Thank you SOOO MUCH!


Tags: cloud