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

Need help with automation, why is this rule not executing?

Fernando Estrada_x98we4

Hey everybody,

I am trying to make a rule that will comment on an issue when it is linked. We already have a rule that links issues, and is working fine, and I'd need my rule to execute when that automation happens. The "allow rule trigger" box is checked.

Above is the rule that clones and links the issues (this part is working and has been for a long time) and the link issue is set to "relates to most recently created issue."

Above is the rule that I would expect to leave a comment in response to previous rule executing, but as I said, it's never executing (as in, the rule doesn't fail, it just doesn't run at all)

Thanks in advance!!

Accepted answers

Vamsi Kandala

Hi @Fernando Estrada

I have tested out the scenario and it is working for me.

As suggested by @Bill Sheboy, the link types should match in order for the second automation rule to trigger immediately.

Here is what I did:

Rule 1:

When issue transitioned from one status to another
Clone issue (same project and same issue type)
Link issue to (most recently created issue and selected 'is cloned by')

Rule 2:

When issue linked (selected 'Link types' as 'Cloners')
Add comment to issue
Checked the 'Allow rule trigger'

Hope this helps.

Thanks,
Vamsi

All comments

Fernando Estrada_x98we4

Something to add - We do not have access to modify the rule that clones and links the issue. It occurred to me that it would be easier to add the "add comment" action to the cloning rule, but sadly that is not an option. Thanks!

Mikael Sandberg

Hi @Fernando Estrada,

Welcome to Atlassian Community!

Make sure that you have checked Allow rule trigger under details, this is needed if you have an automation that is triggered by another one, like in your case.

Rule trigger.png

Fernando Estrada_x98we4

Hey Mikael, that box has been checked since the beginning 😕.

Bill Sheboy

Hi @Fernando Estrada

Have you confirmed the link type in your trigger matches what is happening in the issue?

If you are unable to modify the source rule (which is a good idea for this use case), why not clone it, disable the source rule, and add the comment?

Have you confirmed the rule's scoping? For example, is the first rule a multi-project rule, and perhaps it does not include the project where your second rule is defined.