Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

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

5 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 Dave Liao likes 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}}"}}}

Suggest an answer

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

4 steps to get actual statuses on the Jira board.

Jira   is a powerful tool   that helps teams to plan, manage, and report on their work.   We love using Jira, especially for its ability to track issue progress. But how to monitor the...

1,174 views 10 14
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