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

Global Automation

Rico Meyer

I have multiple Work Management projects. The first one that I created and configured automation rules for works fine. The other projects that I subsequently added simply does not trigger any automation, I have tried:

Single project: Configured the rules exactly as was done in the very first working project - no luck.

Global: no luck

Multiple projects: Selected every one of the projects including the working project - no luck.

Project type: tried every one of the three project types available to me - no luck.

The automation that Im trying to add are basic triggers related to tasks and sub-tasks such as "When chaning the status of a sub-task move the Parent status to the same status".

Any assistance would be appreciated.

Regards

Accepted answers

All comments

Tessa Tuteleers

Hi @Rico Meyer ,

welcome to the community!

Could you describe your trigger / conditions / actions (with screenshot if possible)?

Who is the actor of the rule? Does that user have the necessary permissions in the projects you want to use the rule on?

Cheers, Tessa

Rico Meyer

Hi Tessa

Thank you for the quick response. See attached x2 screenshots, both rules are identical with the same actor and owner.

Not Working.png

Tessa Tuteleers

Hi Rico!

and if I understand, the first rule works, the second doesn't?

- What does the audit log show? Does it simply not trigger at all, or are there errors?

- If it is not triggered at all -> does the automation actor have access to the project? (by default it should have, but you can remove the access, or have issue security in place blocking the actor)

- If it is triggered but gives errors, what is the error?

Rico Meyer

Hi Tessa

The rule seems to trigger but does nothing.

The audit log simply indicates "No action performed" with a further message indicating "The following issues did not match the condition:...".

Audit Log.png

Rico Meyer

For anyone that struggles with the above, I managed to find my problem.

When I added automation rules I added them in a specific project, this means that the automation rules are limited to only this one project. You can change this rule to include multiple projects or even global but this doesn't change anything.

The rule needs to be configured from the start as a global rule then it isnt limited to one project.