Automation Question, How to Link to Ticket C to Ticket A, through Ticket B?

Mario Licup

Hi Folks, I hope I can convey this clearly. We have a tricky situation where if we can get this automation done, it will save my team a TON of headache. 

We need to Link to Ticket C to Ticket A, through Ticket B? 

Ticket C is a project called REI

Ticket B is a bug ticket and can be any project within JIRA

Ticket A is a project called OPS.

we have this new convoluted workflow where someone can request an escalation in Ticket B (bug) which then auto creates Ticket C (REI). Ticket C (REI) goes through an approval process and when approved a Pull Request is created in Git, and when that PR is assigned to my team, Ticket A (OPS) is then created by an in-house app/bot, signaling that the PR is ready for merge and deploy and is always linked to the appropriate Bug ticket (Ticket .

The problem is, Ticket A (OPS) is linked to Ticket B (Bug) and Ticket C (REI) is linked to Ticket B (Bug). In Ticket A (OPS) there is no sign to us that Ticket C (REI) exists and therefore, we cannot tell when one of MANY Ticket A (OPS) is an escalated ticket. We are resulting to spreadsheets and Jira filters, where we once had a total over view through a kanban board.

 

Basically I am asking, Does anyone know how I can get Ticket A to link issues that are linked to ticket B with automation rules? 

So IF Ticket B contains linked issues of Project type (REI) Ticket C, then also link to Ticket A

Hopefully this was written clear enough to understand

Tom Lister_fo1j4e

Hi @Mario Licup 

I think I have this right

B is created. Escalation creates and links to C
A is created. Automation links to B.
You want an automation to link A to C

I've created this which should work but assumes there is only one link to lookup. It may also work more safely if the links involved has specific names.

I can export and send you the json for the rule but there doesn't seem to be a way to attach it to this reply