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

Automation trigger linked issue doesn't work

lh_2023

Hi,

I have plenty of automations that clone an issue A to another project (so we get issue and link both issues (direction A->B). Unfortunately the asset references won't be cloned (IMO it's a bug...) so I created one new automation with trigger "issue linked" that should set the asset custom fields of the desinationIssue based on the values of the Issue. So the first automation triggers the second one but that doesn't work well.

To set the asset custom field of issue B in the second automation I have to use a branch (because issue B is the "destinationIssue").

The automation starts (so get triggered from the first one) and the protocol entry shows that it gets both of the issues right, but then in the branching part it doesn't find any issues.

Is this kind of a cache problem? Any idea?

Accepted answers

All comments

Rebekka Heilmann (viadee)

Hi @lh_2023

can you show the details of the Branch-Action?

Mikael Sandberg

Make sure that you have checked "Allow rule trigger" under rule details on the second automation that runs on issue linked.

Rule trigger.png

lh_2023

I did and the log proves this. The rule is triggered, that's not the problem.

lh_2023

Sure, it's just "Edit issue fields":

lh_2023

(unfortunately - it would be the easy solution ;-))

Rebekka Heilmann (viadee)

I meant the actual branch "Für Zielvorgang"

lh_2023

Actually it does work when I link an issue manually not by using the first automation. So it has to be something between the first and second automation.

Welcome!

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

Quick Links

Find more posts tagged with

automation

data-center

branch

jira-service-management

jira-service-management-data-center