How can I use JIRA automation to link related defects together.

[Kendall Sosnovich]

When users log a Defect via the xray test execution, we have it set up to link that new defect (we are using issue type Bug) to the associated Test and User Story. If you create another defect from that same test execution, it will also link to the associate test and user story. However, the 2 defects are not linked to each other. 

Is there a way to run an automation rule that will link to two defects together? I've tried setting the trigger as when an Issue is Created and when an Issue is Linked, but it have not been successful. 

[Craig Nodwell · Accepted solution]

Hi @Kendall Sosnovich welcome to the community.  Your answer should lay in automation branching. 
I would suggest you have a look at this
jira-automation-branches 
And specifically this
branch-automation-rules-to-perform-actions-on-related-issues 
And one more very specific to what you are trying to achieve
automatically-link-issues-to-other-issues-with-automation-for-jira 

[Kendall Sosnovich]

Hi @Craig Nodwell ,

Thank you for the articles. However, I do not appear to have the "Issue" field under the Edit Issue action. Is this a custom field that needs to be created or a limitation of JIRA Cloud?

[Bill Sheboy]

Hi @Kendall Sosnovich 

What problem are you trying to solve by linking the defects to each other...when they are already linked to the source item under test (i.e. the story)?

Knowing that may help the community to suggest ideas to solve the problem.  Thanks!

Kind regards,
Bill

[Kendall Sosnovich]

Hi @Bill Sheboy 

We wanted a way to holistically see everything, regardless of which issue you are viewing (Story, Test, or Bug).

So to your point, if we are looking at the Story or the Test, we will see all the Bugs created, but we aren't getting the "whole" picture per se, when we are viewing the Bug(s). 

Additionally, having the bugs linked together factors into another automation rule we want to implement. 

Thank you,

Kendall 

[Bill Sheboy]

Thanks for explaining, Kendall.

I think Craig has you on a good path with their suggestion, as once the new bug is created you could use branching and perhaps JQL to go up to the story and then cross-link the bugs from the branch. 

One gotcha to watch for: applying the links in a consistent direction or duplicate links could be added between issues.