You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hello all,
I have 2 parents in Jira and have automation. If i moved sub-task from parent 1 to parent 2, triggered only parent 2. How i can trigger (current)parent 2 AND (previous)parent 1?
I want to check and change status both parents.
Hi @Yuri ,
Welcome to the community!
You have not tagged the hosting type of your instance. As Automation is quiet different in Server / DC / Cloud, it is very important to mention the correct hosting type.
In any case, for triggers that have editted the issue, you can use the changelog smart value.
For cloud, you can use the smart value {{changelog.Parent.FromString}} to get the key of the parent before you moved it to a new parent, and {{changelog.Parent.ToString}} to get the key of the new parent (after change).
Be aware that your trigger must be an "issue editted", with the appropriate conditions, and not "issue moved", I don't think it triggers when you move a subtask to a new parent.
More info can be found here: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-issues/
Hope this helps!
- Tessa
Oh yes. thank you, but now can i somehow change status by this {{changelog.Parent.FromString}}?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey Yuri,
The smart value gives you the key of the issue. You can use that key to find the issue (branch rule action -> related issues -> JQL ) and then use a transition action on that issue.
- Tessa
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.