Link issues based on custom field

[Jack Tucker]

Hi All,

I am trying to link two issues together based on the same custom field in both issues having the same value, this value would be a user. 

Any help is appreciated! 

Jack

[Ste Wright · Accepted solution]

Hi @Jack Tucker 

You need a method of finding other issues to link the trigger issue to - for example...

• Trigger: Field Value Changed
  • Monitor = Custom Field
• Branch:
  • Type = JQL
  • JQL = "Custom Field" = {{triggerissue.Custom Field}} and "Custom Field" is not EMPTY
• Branch-Action: Edit Issue
  • Linked Issues = link to trigger issue

---

This rule...

• Monitors the field in question, to check it's been modified
• Locates other issues which match the Custom Field, and are not empty. The JQL uses a smart value to locate issues which match the same value as the issue that triggered the rule dynamically
• Then uses an action to link any issues found back to the original issue

---

I'm not saying this is the exact rule you need, but should get you on the right track.

If you need more information let us know more specifics :)

Ste

[Jack Tucker]

Thanks for sending this over @Ste Wright I appreciate the help!

My query now looks like the below but I am getting the following error. Any ideas on how to fix this? 

[Ste Wright]

Hi @Jack Tucker 

Sorry, missed this response - is this still an issue?

If yes, is 10771 the field's name, or its ID? If it's the ID, you need to include "customfield_" in front of it.

EG. customfield_10771

Ste

[Elyes Gannoun [Elements]]

Hello @Jack Tucker ,

If you want to display relevant related issues based on current issue values, let me introduce you to our application Elements Overview.

With this application, you can configure a dynamic JQL query that will display in each issue, other issues that share the same configuration (in your case an user custom field).

In addition, you can directly work on these displayed issues thanks to the inline editing we offer. 

Take a look at this demo that illustrates your need (the link is made on the label instead of a user field, but shares the same logic)

If you have any other question, feel free to reach out to me or our support team.

Kind regards,
Elyes

[Jack Tucker]