Automation to link issues with specific labels

Question

Hi Guys,

Want to link my current issue to any specific issue/epic if any user adds a label to the story. For example,

Label name: Release 1.0

If the STR-1111 card has a label Release 1.0, it blocks the STR-2222

How to achieve this via automation. Somehow it's failing with error: You cannot link an issue to itself.

Matthew Day_7dgif0 · Answer

You've captured my intent perfectly. We've been in all-day SAFe I&A meetings, but I will test this out over the weekend.

JD_sjez00 · Answer

Ok @Matthew Day , I'm not sure if I've got it 100% but here is a starting point.

This automation runs every time the labels field is updated. There is a condition to check that the label is log-rotation. If it passes the condition then it searches for all the other issues with the same label and links each of them to the issue that triggered the automation. Below are some more details on each component in rule and also some thoughts on making it more specific:

* Use the field value changed trigger and monitor for labels to be changed
* Using the issue field condition check if the label field contains the log-rotaion label. I've used contains any of as the operator because if you choose equals and there is more than one label assigned to the issue it won't pass the condition. 
* Using a branch rule / related issues look for other issues that already have the log-rotation label assigned to them. I used a JQL for the type of related issue and just put labels = log-rotation for the JQL search.
* In the branch add the link issue action and choose relate to and trigger issue.

A word of caution with this: As you use the label log-rotation more and more it will increase the number of tickets that are linked to your issue. So at some point you might end up with more than 100 related issues. Is there any other criteria you can add to the JQL search in the branch component to make sure only relevant issues are linked? Maybe by creation date or status?

* created >= -52w will only link tickets that were created in the past 52w
* status in ("TO DO", "In Progress") will only link issues that are open

Let me know if that helps

- John

Matthew Day_7dgif0 · Answer

Hi John,

Very simply: labels = log-rotation
Most of my current (very limited) automation triggers off components added to tickets that trigger creation of sub-tasks. Very simple.

I'd like to apply any type of mechanism (labels, components, etc...) that then simply links related tickets (with the same mechanism identifier) without necessarily having them sit in epics that never end.

i.e. if I have 350 servers, and 3 or 4 of them are problematic for log rotation, then applying a log-rotation label would then automatically link the tickets with 'relates to' within Jira.

This way, when someone on support creates a ticket, it would automatically identify other open (or resolved) tickets with the same general identifier.