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 have a lare Project, with epics that have child issues.
I want an automation that every time a Child Issue(A) is created, a "linked issue" is created in another project.
I want to add the name of the epic of the Child Issue's(A) as a lable in the linked issue.
Notes: the epic does not exists in the linked issue's project.
Thanks!
D
Here is something to try. Just an idea to explore.
Create a Variable (action) and equate it to the Epic name. Then update the Labels field with that variable. One potential challenge is converting any spaces in the epic name to "-" or "_". Otherwise you would create a label for each word I think. You could consider setting the variable to the key as well.
Thank you Jack, I see your solution.
I believe my question was incomplete, because, I have several possible Epics. Depending on the epic, I would like to have the name as a lable in an issue in another project.
With a variable, the lable will always be what I set the variable to be, right? It would not depend on which epic the child issue has.
Is there another way to compare and branch check for parent Epic name?
Thank you.
David.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Not sure I follow or not but I think you could use an if/else branch and set variables based on the epic.
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.