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.
Hello,
I need to link a special Epic with a newly created issue by comparing two same fields of the epic and the issue.
Example:
A customer creates a new support issue and types in his customer number in the custom field "customer number". The suitable epic for this customer has already been created and also contains the customer number in the custom field "customer number" and this also is contained in the epic summary.
When customer A1 creates its support ticket the epic of him has to be linked automatically. When customer B3 creates a support ticket, then its own epic has to be linked to the support issue automatically.
Is this possible with Automations?
Can anyone help me to solve this task?
Regards,
Tuna
Hi Tuna,
Yes, you should be able to do that with Automation for Jira.
You can add a Branch using JQL after the trigger fires. The JQL would look like:
Project = ABC and updated >= startOfDay()
Then add an Advance Compare Condition under the Branch. It would look like this:
Then add a new action for Link issues. It will look something like:
Hi John,
thanks a lot for the fast answer!
Unfortunately, this doesn't work for me, because I don't use a branch. The whole automation process should be done in the support issue.
Furthermore the Epic must be linked in its right way as an Epic through the field Epic Link and not as a linked issue.
Best,
Tuna
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Is there a reason you can't use a branch? Can you share the rule that you have so far?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi John,
sorry for my late answer. Here is the working automation rule for my purpose.
Thanks again for the support.
Kind regards,
Tuna
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.