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.
The question is:
Is there a way in Automation for JIRA to automatically link tickets that are within a fixversion to a specific ticket type also within that same fixversion?
I would run this on the scheduler trigger, but the goal is this.
Fixversion is established: lets call it release-abcd
I have a current working automation that when a new fixversion is created it creates a ticket of issuetype called "Release Candidate" and added the created fixversion to it.
If any tickets (bug, task, story) are added to the above fixversion, I ideally want to have something auto link those tickets to the Release Candidate ticket which is also within the same fixversion.
There would be only 1 RC ticket per release and only 1 RC ticket per fixversion.
Is this even possible?
Hi @Larry Katz
To confirm:
------------------
If yes, this is how I got it to work:
------------------
^ Remember for the link type in Step 5 - you are linking from the Release Candidate to the other issue, due to the Branch in Step 3.
You can modify part of the rule depending on your specific need - for example:
------------------
Let us know if this works for you :)
Ste
This is EXACTLY what I needed, and works perfectly, Thanks much! I was looking at the trigger wrong, field value changed for fixversion for sure did it. Much Appreciated.
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.