Automatic rule not being executed after issue clonation

[Carlos Piña López]

Hi, I recently created a couple of rules for a Jira project.

1. A manually executed rule that clones an issue.
2. An automatic rule that is executed after an issue is cloned.

The start of the second rule is as depicted in the following image.

I tried these rules in a test repository and everything worked fine.  However, after migrating the rules to another repository and manually triggering the first one, the second one didn't automatically trigger, and the audit log was empty.  Could this be related to some configuration in the second repository or something like that?  The rules in the second repository are identical to the ones in the original one, so we have no clue about what could be happening.  If you have any idea about what could be happening please let me know.

Thanks in advance for the answers.  If you need more context feel free to ask.

[Marc - Devoteam · Accepted solution]

Hi @Carlos Piña López 

In the rule that needs to trigger after the manual rule is the check box enabled on the rule details.

"Check to allow other rule actions to trigger this rule. Only enable this if you need this rule to execute in response to another rule."

[Carlos Piña López]

Hi, Marc.

That was it, apparently that checkbox reset when the rule was moved to the other repository.  Thank you very much for your answer, I'll mark it as accepted.

Have a great day.