nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Linking Epics with Labels Via Automation

Curtis Hill

Hey All,

I'm bulk creating sets of ~20 epics that are all interconnected to each other. I believe my best option would be to use the label field as the connective tissue between the epics. I'm currently using an automation rule that I kick off manually which searches for any issues that contain the first epic. Then I use a branch rule that reads JQL which identified the downstream Epic via a label. Lastly I'm using the "link issues" to try to grab all issues with the first label.

If I try this last step with just an issue key the rule runs successfully so I believe I have a syntax issue with how I'm trying to grab the epic in the final step. I'm currently using {{issue.labels.match("(EpicImport1)")}} to try to grab any epic with the label EpicImport1.

Images attached are a small scale version of what I'm trying to do. Thanks in advance for any advice, alternatives, or solutions!

Accepted answers

Bill Sheboy

Hi @Curtis Hill -- Welcome to the Atlassian Community!

To which issue are you trying to link with that rule action?

That field in the Link Issue action takes an issue key, but the match() function returns text you are searching for. In this case, it could only be "EpicImport1" and that is not an issue key.

Do you instead want to link to the trigger issue?

Kind regards,
Bill

All comments

Alexis Robert

Hi @Curtis Hill ,

looks like you're on the right track with the Smart Value to match this label, I'm wondering if maybe this is juste an issue with quotes.

Could you try this value instead :

{{#issue.labels.contains("EpicImport1")}}{{/}}

Let me know if this helps,

--Alexis

Curtis Hill

Hey @Alexis Robert, thanks for responding! When running with your value I'm getting this error. I know I have permission in my project so I suspect this value is not able to see the epic with the attached label.

Bill Sheboy

Hi @Curtis Hill -- Welcome to the Atlassian Community!

To which issue are you trying to link with that rule action?

That field in the Link Issue action takes an issue key, but the match() function returns text you are searching for. In this case, it could only be "EpicImport1" and that is not an issue key.

Do you instead want to link to the trigger issue?

Kind regards,
Bill

Curtis Hill

Hi @Bill Sheboy

The info text below the link field says I can use a smart-value and I think that is what I need to use in this situation. I can't link to the issue that triggered the rule as that would just link my base epic to itself. Issue keys work technically but they require me to manually find the epic. Doing that doesnt really save me any time since I'm already in the epic and I could manually click the link button. Given the scale of the tickets I need to create and link that will not be a viable option.

All that to say I think the smart field option is the way forward but I'm not sure how to build the connective tissue. My best guess was trying to detect a label but I'm not sure that is actually possible with the smart-value.

There is an example automation for linking an issue that is commented on to a ticket, which is close to what I'm trying to do. If this is possible I think I just don't know the proper syntax to do what I want to do. I added an image of the example automation rule below.

Thanks for your time!

Bill Sheboy

Okay, that looks better as the match result might be a valid issue key in a comment.

I was noting the literal value "EpicImport1" you showed is not an issue key, and so the linking could not work.

So...are you putting issue keys in the labels to do this, or are you using "tokens" to refer to an epic, such as "EpicImport1", which must then be found?

Perhaps if you show some sample data that will clarify things for the scenario, with the keys, labels, etc.

Curtis Hill

I'm not sure I fully understand but given the context the "token" approach sounds closest to what I am doing. Maybe this breakdown will provide more context?

If an Epic has label EpicImport1

Branch and use JQL to search for all epics with the label EpicImport2

Then Finish to Start Depended by link "Smart-value that can detect the label EpicImport1"

The goal is to link all Epics with the label EpicImport2 as downstream dependancies of all Epics that have the label EpicImport1.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud