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; } } }

Creating automation rules for specific Jira tickets

Luke_5b0c79

Hi, I'm trying to create an automatic rule that does the following, but cannot figure it out:

1/ For selected issues only (e.g. issue numbers, let's say, T01-T12 or whatever)

2/ When another issue (or issues) is linked (via any link type) to any of said selected issues

3/ Then notify a specific user (potentially other actions too, but this is fine for now!)

How do I go about it? Is it perhaps better to flag/tag/categorise those specific tickets somehow first, or maybe preassign them to a user (worried user will get changed, though!) or via some other method? I can't work out the right steps to get selected issues/tickets.

These issues that I need to action will never (or rarely) be closed as each represents a component type within our software suite. I want to alert the lead dev for each component whenever an issue (e.g. bug, feature request) is linked to it.

Thank you.

Accepted answers

All comments

Trudy P Claspill

Hello @Luke

Welcome to the Atlassian community!

Are the tickets being linked together all in the same project, or potentially in different projects?

Is this for a Company Managed project or a Team Managed project?

Luke_5b0c79

First off, thank you for such a fast response to my first ever community question and the kind welcome!

Right so, the tickets/issues representing web components are all sitting under one project (let's call it 'Base'). However, issues being linked to the issues in Base will be mostly from other projects (idea in a nutshell is other live projects are reporting issues/bugs/enhancements on their custom implementations of Base code, so some will get fixed in the Base then rolled back out for all projects).

Base is a Company Managed project (all projects should be, in fact).

Trudy P Claspill

There is an Automation Rule Trigger for "Issue Linked" when an issue link is created.

https://support.atlassian.com/cloud-automation/docs/jira-automation-triggers/#Issue-linked

However, it is a tricky rule to master.

Rule executes when an issue is linked to another issue. {{issue}} will always refer to the source issue, so if ISSUE-A is blocked by ISSUE-B, this rule will execute on ISSUE-B. To access ISSUE-A, use {{destinationIssue}}, and to access the link type, use {{linkType}} (e.g. {{linkType}}

It depends on what is considered the "source" issue and the "destination" issue. This is determined by the link relationship. From the Issue Linking page where Link types are defined...

Screen Shot 2023-01-12 at 1.00.46 PM.png

The issue that shows the "Outward Description" in its Linked Issues section is the one that "triggers" the rule.

Your rule would have to be set to run against each project where an issue in that project might get linked to an issue in the Base project, and where that issue would have the Outward Descriptions side of the link relationship.

After detecting that, you would need to determine if the link was to one of the issues that you are concerned about. I haven't quite worked out how to do that.

I can keep looking into the solution, but it will be a lower priority task for me. It may take me some days to figure it out completely.

Luke_5b0c79

Hi Trudy, thanks so much. I'll try to figure out out from the puzzle pieces you've kindly given me thus far. If I get stuck maybe I can pop back and holler! Really appreciate your time and help.

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