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 An Idea Ticket to a Delivery Ticket Fails to Trigger Automation Rule

Ali Ishaq_zl12i9

I am trying to create an automation rule that is based on the linking of a Jira Product Discovery board Idea ticket to a Jira Epic or Story. My goal is:

When Issue is Linked by type Polaris datapoint issue link, Polaris issue link

For Destination Issue

Then Edit Issue Security Level

Here is my current automation configuration:

The automation works only if I add the link from the Jira project Story/Epic ticket, as shown below.

However, my main use case is going into Jira Product Discovery to link to an existing ticket in a Jira Software Project, as shown below.

This does not kick off my automation, because the link type is not one of the ones defined in the automation, as shown below.

Is there an rule that will allow me to update my automation to handle the link being initiated from the Product Discovery board?

Accepted answers

Bill Sheboy

Hi @Ali Ishaq -- Welcome to the Atlassian Community!

With the issue linked trigger, and a type of Polaris issue link (i.e., implements or is implemented by) the rule will trigger from two possible scopes:

A rule defined in the software project with single-project scope, although it will not be able to access the details of the JPD idea.
A rule defined in the global rules list with a multiple-project (or global) scope, and it will be able to access all issues involved.

Apparently there was a design decision that because JPD ideas could also link to other ideas (or issues with other link types) that the Delivery Ticket linking feature would not fire the Issue Linked event for rules.

Kind regards,
Bill

All comments

Mart Postma

Hi @Ali Ishaq

It is relatively new that Ideas are shown like that on the Jira side.

If I remember correctly, previously the Polaris issue link types used to link JPD issues with their delivery tickets, where:

"is implemented by"
"implements"

It's been a while since I used this in my automation rules, so not sure if this is still accurate and whether it can actually be used. But might be worth a try.

Ali Ishaq_zl12i9

Yes so that works only if I initiate the link from the Jira ticket. If I initiate the link by "Linking to Existing Ticket" in JPD's Delivery ticket view, then the automation will NOT be kicked off.

Bill Sheboy

Hi @Ali Ishaq -- Welcome to the Atlassian Community!

With the issue linked trigger, and a type of Polaris issue link (i.e., implements or is implemented by) the rule will trigger from two possible scopes:

A rule defined in the software project with single-project scope, although it will not be able to access the details of the JPD idea.
A rule defined in the global rules list with a multiple-project (or global) scope, and it will be able to access all issues involved.

Kind regards,
Bill

Ali Ishaq_zl12i9

Gotcha. So essentially there's no way to automate this from the JPD board then?

Bill Sheboy

Correct; for the scenario you show you may want to try the global or multiple-project scope rule and add the conditions / branching needed to access the correct issues.

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud

jira-product-discovery

jira-automation

jpd