Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Use Jira Automation to amalgamate data from multiple child issues into Parent

Michael Razey
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!
September 28, 2021

Hi, I'm relatively new to Jira automation, especially when trying to do something relatively clever / complex so reaching out for a bit of guidance from any experts out there!!

For context, we have a Jira project / kanban board on which we manage portfolio Initiatives.  Each initiative will be linked to one or more Epics / Stories / Tasks residing in different Jira projects, using the hierarchy link type (parent of, child of) - e.g. Initiative is parent of Epic.

I am trying to use Jira automation to pull through the fixVersions defined on the child issues and amalgamate these into a text field on the initiative.  One Initiative could be realized via multiple Epics, which themselves are being delivered in different version releases.

As the fixVersion on the child issue could be updated at any time, we're currently looking to trigger the automation on a schedule (daily) rather than upon issue creation or linking.

Ideally, the fixVersions would be de-duplicated in Initiative text field but listing the child issue key + fixVersion for each would also be a viable option.

I have the following rule configured...

Rule.JPG

And it has ran successfully...

Audit log.JPG

But the target field in my Initiatives has not been edited / updated.  I'm sure I have missed something but cannot figure out what!  Any help / guidance would be very much appreciated.  Cheers, Mike

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 Champions.
September 28, 2021

Hi @Michael Razey 

To help clarify what you are trying, would you provide images of:

  • what is the JQL for your scheduled trigger
  • what value are you setting to the created variable, childFixVersion
  • what value are you setting to the edited field, Module Version(s)

Of note: I see in the log that many issues are getting picked up by the Lookup Issues and the Scheduled trigger.  Automation rules can only process up to 100 issues per trigger/component, so you may want to rethink your approach.  Perhaps try multiples rules (by hierarchy level) with staggered start times, and allow the aggregate values to percolate up to the top.

Kind regards,
Bill

Suggest an answer

Log in or Sign up to answer