Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,554,036
Community Members
 
Community Events
184
Community Groups

Inherit Team from parent issue

I'm trying to use automation to set the team of a new issue (using advanced roadmaps) based on the parent issue, completely similar to: Solved: Inherit Team field from parent issue using Automat... (atlassian.com).

However in my case the audit says that the rule was successful but the team field stays empty, even though the parent team is defined.

In the above example in the JSON query they use issue.epic. Since our hierarchy is:

capability

 - feature

    - story

 

I've tried issue.parent as well, without results. Anyone an idea on how to solve this or get the team id assigned in a different way. Some tips on how to trouble shoot JSON are also appreciated. 

the code for edit issue:

{
"fields": {
"Team": "{{issue.parent.team.id}}"
}
}
}

0 answers

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events