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 All -
I have an odd request for help.
Scenario:
Bug ticket gets created (Ticket A)
Wrapper ticket gets created that then houses Ticket A along with other relevant bug tickets (Ticket B)
Once Ticket B gets to a specific status, a built in automation job activates to clone Ticket B into a different project (Ticket C) in which the work to fix the specific bug on a specific environment and version gets assigned to the specific group needing to do the work. Currently, the automation task is setup to when it clones from B -> C, it sets the link to "Child ticket of..". Ticket C currently has no visibility to Ticket A
Question:
Is there a post function or automation component available to link Ticket A to ticket C upon ticket C's creation?
Hi Drew,
Try this out:
Please let me know if it works for you.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.