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.
Most automations work with individual issues but it is sometimes useful to copy information into a sub-task from it's parent issue.
How do I copy information from a parent issue into a sub-task?
First things first, a quick explination of how smart values work in Automation:
As a chain of components execute in an Automation. As each step executes, it writes any relevant details into what we call the “context object”. This is the object from which smart values are pulled.
Most automations trigger on some manipulation of an issue, so it is often the case that {{issue}} exists within this context object. Lots of actions implicitly read this {{issue}} value to understand what issue to operate on.
Now to answer the actual question, How do I copy information from a parent issue into a sub-task?
Given the above information about the context object, let's assume that `{{issue}}` currently refers to a Jira sub-task. In that case, accessing the parent is as simple as using the `{{issue.parent}}` smart value.
Details about this and other smart values can be found in our docs here: https://support.atlassian.com/jira-software-cloud/docs/smart-values-general/
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.