Hi,
I have plenty of automations that clone an issue A to another project (so we get issue B) 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?
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.
Make sure that you have checked "Allow rule trigger" under rule details on the second automation that runs on issue linked.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @lh_2023
can you show the details of the Branch-Action?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I meant the actual branch "Für Zielvorgang"
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Odd. Looks normal to me and should work as intended.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.