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.
Hi there!
So, I'm trying to set up an automation that creates all of the stories that our team will need once they manually create the Epic. We've set up a "template" Epic in order to pull the stories from there. The issue that I'm running into is that I can't figure out how to pull the description from ABC-123 into the new issue that is being created. We'd basically like to copy the description that's already been written into the new story that's being created.
Is it possible to do this? I'm on Jira cloud. Thanks!
Hi @Jane Ellis
Would you please provide a bit more context: is ABC-123 the trigger issue (epic), or something else?
Kind regards,
Bill
Hi @Bill Sheboy
No, ABC-123 is not the trigger issue - it's a story not linked to the new issues at all.
My team is creating an epic manually, let's call that ABC-456. Once ABC-456 has been created, I have an automation set up to create the 12 issues (all stories) under it that they will need.
I'd like to copy the description from ABC-123 into the new stories that were created as children for ABC-456.
Does that make more sense?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for clarifying, Jane.
As the ABC-123 issue is unrelated to the others, it makes this a bit more challenging to solve. The easiest way to do this is using the Lookup Issues action, with JQL to get at your ABC-123 issue. Please add that action before you create any child stories. And then reference the lookup in the issue create of the child stories as they are added to the epic with {{lookupIssues.first.description}}
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.