Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

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

Mario Licup
Contributor
December 16, 2022

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 B).

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 :)

1 answer

1 accepted

1 vote
Answer accepted
Tom Lister
Community Champion
December 20, 2022

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.

Screenshot 2022-12-20 at 12.05.19.png

Screenshot 2022-12-20 at 12.07.26.png

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

Mario Licup
Contributor
December 23, 2022

Hey Tom, thank you so much for taking a crack at this! I will implement this and give it a shot. 

So in Ticket B, there can be several linked issues. I only need to target Ticket C (REI) and link it to Ticket A (OPS). Also, if it helps any, Ticket B (BUG) will always be "blocked by" Ticket C (REI) if that is something we can look for? or How can I query for just the tickets that start with "REI" ?

Tom Lister
Community Champion
December 24, 2022

Hi @Mario Licup 

You can add the link type (case sensitive) to the lookup

issue != {{triggerIssue}} AND issue IN linkedIssues({{destinationIssue}}, "is blocked by")

And could also try adding a check on the summary

issue != {{triggerIssue}} AND issue IN linkedIssues({{destinationIssue}}, "is blocked by") AND summary ~ "REI"
Tom Lister
Community Champion
December 24, 2022

There is JQL variation on this. Less sure how this will work

Screenshot 2022-12-24 at 13.23.54.png

Happy Holidays 

Suggest an answer

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

Atlassian Community Events