Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Jira automation - linking issue due to ID connections .


We are working on a few projects, the main project is run by Service management and the other projects are on Software.

I'm looking to connect the tickets between all the projects with a customer ID which we add to the ticket labels. 

For example- 

1) Issue created at any project 

2) adding the labels including the ID for it 

3) checking automatically if there is an existing ticked that equals to the ID at any project.

4) linked the issues automatically.


What is the automation I need to use?

1 answer

0 votes
Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 08, 2023

Hello @Tim Shirazi 

Have you tried to construct this automation? If so, show us what you have so far.

Is the customer ID that you are adding to the ticket mixed in with other values that have other purposes in the Labels field? If so, that will make it harder to find the one label that has the customer ID.

Is there ever more than one customer ID for a given ticket? If not, have you considered using a separate Customer ID field to record that value? That would make it easier to find tickets/issues with the same value.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events