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

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

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
4,455,374
Community Members
 
Community Events
175
Community Groups

Search for issues in other projects and automatically link them when at least one component matches

Hi,

I`m searching for hours and still struggle to find a solution.

When a ticket is created / editted  in Jira Service Management and a components gets assigned, I want to search for issues across Jira that have at least one matching component name and link those automatically to the JSM ticket.

  • Support ticket -> component "google"
  • Search for all tickets in projects A,B,C that have component "google"
  • Link issues found to JSM ticket ("relates to")

Thanks for help!

1 answer

1 vote

Hi @Thomas 

One way to do that would be with an Automation for Jira rule...with some limitations:

  • This will require a global/multi-project scope rule, and execution of such rules is limited by your Jira license level.  Please discuss that with your site admin as they will need to create the rule and to check on limits.
  • Automation rules can only process up to 100 issues, and so if you expect more than that this approach will not work
  • And...do you expect your Component values to change for the JSM ticket?  If so, you will need a more complex rule to add/remove links.

 

A simple rule to do this (assuming no later changes to Components) would be:

  • trigger: issue field changes for Components
  • condition: project is your JSM project
  • branch: on JQL for matching issues in the projects which have the trigger issue's component
    • action: link issue to the trigger issue

 

Please take a look at this automation documentation and examples to learn more before trying this:

Kind regards,
Bill

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events