Rule doesn't work with "relates to" link type

Question

Hello!

I need to set a label to a task when it is linked to a task from a certain project, if issue type equals "is chilld for" or "relates to".

I found that my rule is not working with link type "relates to", but the same rule with link type "is child for" works correct.

Example of the rule that works:

Log from issue:

But if i change trigger to "relates" and condition to "types: relates to Match: project = IL" it's not working:

Log:

What i've checked already:

1) The task in the IL project fits the condition exactly, I checked the result of the JQL query search manually.
2) I tried using if/else condition instead of checking the linked task — that doesn't help.
3) When I choose a link type in the condition, there are two "relates to" options available in the dropdown list, I tried to use both

4) Also as you can see on a last screenshot i've tried to use two different rules for each other link type.

The result is the same everytime, i see that "the following issues did not match the condition" in audit log:

Has anyone encountered anything like this?

Backbone · Answer

Hi @Fabian Lim!

Thanks for the reply, I made a similar rule in global automation, but it didn't change anything.
I noticed that if i set the trigger "issue created" instead "issue linked", a similar rule would work. However, my rule should also work when two tasks already exist and the user just merges by linking.

I have a suspicion that the rule can't check linked issues by the "Linked issue match condition", because this task was linked in the beginning of the rule, while the rule checks the already existing parts of the task, so to speak. But this is just an assumption.

What do you think about it?
I'm attaching a screenshot of the logs, in which in case of success the link type was selected "is child for", and in case of inactivity "relates to". Maybe it will be helpful.

p.s. Plz ignore the fact that the Atlas project is now listed instead of the IL project, this is a test space.

Fabian Lim · Answer

Hi @Backbone

Can you confirm that your rule is set to run for multiple projects? You need to do this from the global administration and select the projects that are being affected by this rule. In this case the and and il projects.

Link: https://blog.codebarrel.io/automation-rules-can-now-be-restricted-to-run-in-multiple-projects-910594bee2f0