How to link tickets based off of the same custom field value in different projects

rneill19 March 22, 2024

Hi!

I would like to set up an automation rule that links tickets in Project A to tickets in Project B that have the same value for a custom field called "Customers Affected".

Basically what I'm hoping to do is when a story ticket in Project A gets created and has a specific value for "Customers Affected", it will link to an Implementation ticket in Project B that has the same value for "Customers Affectted". 

Any help is appreciated here, thanks!

1 answer

1 accepted

1 vote
Answer accepted
Kalyan Sattaluri
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
March 22, 2024

Hello @rneill19 

You can set up a rule in Project A with trigger = issue created ..I think you may also have to specify the project scope as both project A and project B... (confirm)

next action = refetch issue to ensure your rule has the field's value in hand.

then action = lookupIssues , give sample JQL -> project = B and "Customers Affected" = "MY VALUE"

then action - link issues -> This issue, "relates to" and give smart value {{lookupIssues.key}}

Please try and let us know if issues, share screenshot / audit logs so community can help.

rneill19 March 22, 2024

Can I use a smart value in my lookupIssues JQL action assuming I've created a variable for it?

Create variable:

Variable name: CustomersAffected

Smart value: {{issue.Customers Affected}}

And: Lookup issues:

"project = B and "Customers Affected" = {{Customers Affected}}

rneill19 March 22, 2024

^That worked actually! And overall worked as well! Thank you so much for your help Kalyan!

Like Kalyan Sattaluri likes this
Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
March 22, 2024

Hi @rneill19 

What do you want to do if the custom field is set (or changed) later, after issue create?

Kind regards,
Bill

rneill19 March 22, 2024

Hey Bill,

This wouldn't apply to this situation! The value of Customers Affected wouldn't be updated on either ticket.

Like Bill Sheboy likes this

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Site Admin
TAGS
AUG Leaders

Atlassian Community Events