Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

How can I link a suitable Epic via Automation when an issue was created by a customer?


I need to link a special Epic with a newly created issue by comparing two same fields of the epic and the issue.


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?


1 answer

0 votes
John Funk Community Leader Jun 04, 2021

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.



John Funk Community Leader Jun 04, 2021

Is there a reason you can't use a branch? Can you share the rule that you have so far? 

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Marketplace Apps & Integrations

Jira issue check and more advanced commit verifications for Bitbucket DC

Pre-receive hooks that verify the Git commit message, the modified files, and implement similar code change controls used to be requirements of large enterprises working in regulated industries only....

55 views 0 3
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you