Automation to roll up Sprint End date and Story Points to Epic (Parent)
Asked by Devender Singh:

Hi All, I am trying to create an automation to roll up Last Sprint End date to the Epic as End Date and Sum of child story points.

In Automation Log the rule runs without errors, however no change in Feature.

For Testing purpose I have manual trigger, however I plan to change it to scheduled once every day.

NOTE: This is JIRA Server edition

![JIRA Automation Feature Roll up.png](https://community.atlassian.com/t5/image/serverpage/image-id/285665i4148F93601CD6F13/image-size/large?v=v2&px=999 "JIRA Automation Feature Roll up.png")


Answers:
author: Bill Sheboy
body: Hi [@Devender Singh](/t5/user/viewprofilepage/user-id/3590857)

As [@Tim C](/t5/user/viewprofilepage/user-id/4438063) noted, you were trying to use the {{lookupIssues}} smart value and the Lookup Issues action is not available for your version of Jira Server.

Two other possible work-arounds for your scenario are:

* Create JQL to gather the issues needed, and call a REST API function with the JQL to search for them...using the Send Web Request action. Then you can get the value from the response.
* Use the bulk-handling issues feature (e.g., scheduled trigger or branches) with the {{issues}} smart value. As you want this value to edit an issue, you will need to structure the rule in such a way that you can branch to the issue which needs an edit, and/or use multiple rules.

There are other community posts on doing what you ask, and so if you search you may find additional details on these techniques.

Kind regards,  
Bill

comments: author: Bill Sheboy
body: Hi [@Devender Singh](/t5/user/viewprofilepage/user-id/3590857)

I am following up to check if the responses answered your question.

Thanks!


author: Colton_Kosicek
body: **Can you use variables in your older version**? You can set the trigger to be daily but will cost you an automation to potentially run for every issuetype if you don't have exit loops so it will burn through a lot more unnecessary cycles. i use sprint change as i have multiple cascading automations in the same automation that trigger.

Sprint value changes on story - update story due date and now check the "parent" due date and update based on the child's oldest. This stops it from having to care about every child issue in the same automation and just checks if the change on the child would impact the parent.

I have a very similar automation that updates the level 2 parent in our environment as well  
![automationVariable.JPG](https://community.atlassian.com/t5/image/serverpage/image-id/285690iBF4FDC8239741777/image-size/large?v=v2&px=999 "automationVariable.JPG")

MinusTwoWeeks

{{DueDatebasedonSprint.minusweeks(2)}}

![AutomationPart2.JPG](https://community.atlassian.com/t5/image/serverpage/image-id/285688iAB1947D12E42555F/image-size/large?v=v2&px=999 "AutomationPart2.JPG")


author: Tim C
body: Hi [@Devender Singh](/t5/user/viewprofilepage/user-id/3590857)

I think you're missing the important step to actually do the "lookupissues" action.

If you're triggering from the Epic itself - then you'll need to use JQL to find the items which sit under the epic .... e.g.

"Epic link" = {{issue.key}}

If you also want to include sub-tasks in your results then you'll need something like this ...

![Screenshot 2023-10-11 145055.png](https://community.atlassian.com/t5/image/serverpage/image-id/285666iD431AA9AD53EEDA3/image-size/large?v=v2&px=999 "Screenshot 2023-10-11 145055.png")

I hope this helps?

comments: author: Devender Singh
body: I do not see that option. We are on server Jira v8.22.2 is the reason ?


author: Tim C
body: Yeah, apologies ... looks like this feature is only available on:

* In Automation For Jira (A4J) 9.0.1 and in Jira 9.11.0 (or Jira Service Management 5.11.0)
* Only for Data Center customers (The Server license does not include this feature)

To benefit from this feature you can:

* either upgrade A4J to the latest version on any Jira DC version from 8.20.0, via the Settings \> Manage Apps \> Manage Apps\* page
* or upgrade Jira to 9.11.0 (or Jira Service Management to 5.11.0)

More info ...

[https://jira.atlassian.com/browse/JIRAAUTOSERVER-53?focusedId=3333220\&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-3333220](https://jira.atlassian.com/browse/JIRAAUTOSERVER-53?focusedId=3333220&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-3333220)