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

The trigger when issue linked trigger not works with "related from" or "is blocked by" options

Sedrak Khachatryan

Dear all,
I have automation with the trigger "Issue Linked" for all link types.
But the trigger not works when the issue is linked as "related from" or "is blocked by" options. With "relates to" or "blocks" options it's working, can't figure out why.
Can Someone help with this?

Also, the Check allows other rule actions to trigger this rule. Only enable this if you need this rule to execute in response to another rule being turned on.

Accepted answers

Trudy P Claspill

Hello @Sedrak Khachatryan

What exactly do you mean when you say the rule "doesn't work" for those types of links?

Is the rule getting triggered?

If it is getting triggered but the results are not what you expect, what exactly is happening that is not what you expect? What does the rule Audit Log say for those executions?

Please show use the details of each step of the rule.

All comments

Ravi Sagar _Sparxsys_

Hi @Sedrak Khachatryan

Share your rule. Links are bidirectional, may be your rule has some JQL that is limiting the issues based on one of those outward or inward link type.

Ravi

Sedrak Khachatryan

Hey Ravi
Thanks for the suggestion, I've updated the question. Also, there is no any JQL in the rule.

Trudy P Claspill

Hello @Sedrak Khachatryan

What exactly do you mean when you say the rule "doesn't work" for those types of links?

Is the rule getting triggered?

If it is getting triggered but the results are not what you expect, what exactly is happening that is not what you expect? What does the rule Audit Log say for those executions?

Please show use the details of each step of the rule.

Gautham H

I noticed that some of my Jira cloud automation rules with the 'Issue linked' trigger were not getting triggered today and realized that it was due to an active Atlassian incident Delayed execution of Automation Rules.

I recommend checking the Atlassian status page for any active incidents related to automation.

Ahmed Aftab_o7ec4k

Hi @Ravi Sagar _Sparxsys_
I am facing a similar problem.

The linked issue trigger only works when issue link "Blocks" is used. For cases when the issue is linked as "is blocked by" the automation rules don't trigger at all.

It is mentioned in the linked issue trigger that rule will always refer to the source issue. I am unable to set it for destination issue.

Your help in this matter is highly appreciated! Screenshot 2024-01-08 132832.png

Moheeb Qupty_rjyyg4

The rule "Issue Linked" isn't triggered at all with "inward" link type (e.g. "is blocked by")!

Although we specify all "Link Types" and moreover you can see from drop down list of the "Link Types" the inward link type aren't in the list!

So it seems for some reason this rule trigger doesn't work on inward link types only outward and it's ready a big minus.

Does anyone knows the reason?

Trudy P Claspill

The Issue Linked trigger is a special trigger.

When an issue link is created there are two issues involved. Most triggers are activated by a change on a single issue.

So the Issue Linked trigger will be triggered for only one of the issues, but will let you reference both of the issues. The issue that is the one that triggers the rule is referenced by the {{issue}} object, while the other issue in the link pair is referenced with the {{destinationIssue}} object.

The triggering issue for the rule is not based on which issue you are viewing when you create the link.

The triggering issue will always be the one that appears under the Outward Description for the link type in the Linked Issues section.

If issue A "is blocked by" issue B, then issue B will be the triggering issue for the rule

If you look at the details of issue A, under the Linked Issues section you would see the heading "is blocked by" and issue B would appear under that heading.

So, if you are in issue A and you create a "is blocked by" link to issue B, it is the change in issue B that causes the rule to be triggered.

Within the execution of that rule, issue B would be accessed using {{issue}} and issue A would be accessed using {{destinationIssue}}. When you are adding steps to the rule, you must keep in mind which issue is the triggering issue and which is the destination issue.

If the Outward and Inward descriptions are the same, as is the case in the Relates link type, that is another special case.

Moheeb Qupty_rjyyg4

Hi,

First thanks for the detailed reply.

What you have described all good and true but you are missing the point I want to make.

You said:

"So, if you are in issue A and you create a "is blocked by" link to issue B, it is the change in issue B that causes the rule to be triggered."

The problem and the main point here that nothing is triggered, no rule is triggered at all in case we are in issue A and created a "is blocked by".

I have no problem to refer to the right source (issue B in this case) and right destination (issue A) but no triggering in order to do that.

As I mentioned again, the only trigger is when you choose "blocks" from issue A (source) and issue B (destination); it's like they are enabling the triggering when the current issue we are viewing (issue A) as the source while when the current issue we are viewing is the destination the rule doesn't trigger.

Automation rules goal is to simulate user actions, and user can and will create links regardless if the direction from the current issue while the rule is restricted in that sense and that a big MINUS.

Moreover if you look at the dropdown list in the "Issue Types" for the rule is does includes both directions under the link type name (e.g. Blocks/is blocked by, blocks) and it sounds like it would triggered both but it doesn't!

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-service-management-cloud

jira-service-management