Automation to roll up Sprint End date and Story Points to Epic (Parent)

Question

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

Bill Sheboy · Answer

Hi @Devender Singh

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

Thanks!

Bill Sheboy · Answer

Hi @Devender Singh

As @Tim C 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

Colton.Kosicek · Answer

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

MinusTwoWeeks