Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Setting next-gen Epic parent in jira automation

I would like to create the below rule using Automation for Jira:

  • When an issue transitions to 'in progress'
    • create a new task in next-gen 'Project EPMO'
      • and link task to next-gen epic 'EMPO-40'

The rule works up until point 3. I'm not able to link the task to an Epic. 

I've tried setting the 'Epic Link' field - but it did not recognize epic link.
I've also tried setting the field 'parent' via JSON but said 'data was not an object'

Any suggestions? 

 

image-20200107-014029.pngimage-20200107-014119.png

1 answer

1 accepted

6 votes
Answer accepted

Seems I've solved by own problem. 

If anyone is interested, to update the parent of a child issue in next gen projects, you need to reference is the Issue Id of the parent:

{"fields":{"parent":{"id":"36768"}}}

 

The rule works below: 

Working rule.PNG

How could I format this so that its the trigger issue, which is the epic? I am trying to automate a set of tasks that are created for each epic created. 

Like # people like this

@Natasha Denny Thank you SO much for following up and posting your solution - I was able to use your discovery to solve an unrelated problem. I'm eternally grateful! 

Like # people like this

@Taylor Snow - Not sure if you're still looking for an answer on this, but the easiest way to do this is to set a variable at the beginning of the automation, with the value being {{issue.id}} (I named my variable {{parentID}}.  This will let you extend this value into some of the repeated nested flows.  Then when referencing, the example above should look like this to set the parent:

{"fields":{"parent":{"id":"{{parentid}}"}}}

Like Charles Amschel likes this

@Jonathan Sheetz Thank you for this! I'm very new to this stuff. Your comment made all the difference and will save me a ton of work. 

@Natasha Denny Thank you so much, that worked like a charm!

For anyone else finding this solution, you also can set the key of the Epic instead of the ID like this:

{"fields":{"parent":{"key":"TS-123"}}}

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Team-managed projects

An update on team-managed projects customer feedback – November 2021

Hi! My name is Eoin and I'm a product manager working on Team-managed projects in Jira Software Cloud. We're continuously improving and updating Jira Software and feedback from our customers is ...

1,442 views 0 8
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you