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.
I set up a JIRA Automation rule in order to automatically create epic & issues when some personalized fields are filled. Please see below the rule.
On the else / if part of the rule, I create first an epic and then a ticket. I would like this ticket to have the previous created epic as epic link. How could I do so ?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Malvina Garnier
Were you able to make this work? I'm looking to implement the exact same thing and would really appreciate some help!
Thanks!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Antonio,
Sorry for the late answer but yes, I do. See my last comment for the solution ;)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Malvina Garnier , if you are asking how to create an epic and underlying stories within an automation rule there are a number of existing posts that could help. I found this one with a quick search that might help - Automation-Set-Epic-Link-on-Story-to-Epic-created-in-the-same-automation
if Iām missing the mark please LMK.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
In looking at your screenshot I think the key piece you are missing is the Branch component once epic is created.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Jack. Thanks for your answer. I'm really sorry but, I took a look on the post you advice me to check and I tried to reproduce what is done but I may do something wrong and it still doesn't work :'(
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yep as your solution depicts the branch component is the key.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes, and...to what Jack describes:
One alternative to using the branch on recently created issue is to instead set the epic link to most recently created issue's key directly: {{createdIssue.key}}
Kind regards,
Bill
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I tried different option but no one works. Maybe I should you the 'More options' field ? Hope I will find help here :)
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.