Hi Team,
We created the rule that if member XY is assigned, a specific project needs to be added. Unfortunatly, the rule is not working properly, for some Tasks it’s working, but not for all.
Rule:
Project:
It’s running if we do it manually, but that’s not how it should work.
Any ideas?
Thank you
Tim
@Tim_Schumann - welcome to the forum! The rule you set up looks correct (although do you want subtasks to also be added to the other project? this rule will add tasks and subtasks to the new project as top-level tasks).
Could you open one of the tasks that failed and check the activity log?
Hi @Tim_Schumann,
Can you clarify what you mean by this? Are these tasks being added by a form or another project? Is the assignee being added by a rule?
You may need to check “Allow this rule to be triggered by other rules”.
You can find it by clicking the ellipsis next to “Run on tasks and subtasks”.
Christine
@Stephen_Li Yes, I want to add Tasks & SubTasks to the other project. I also checked the activity log and for some random Tasks the rule is not running.
@Christine_Bolton These Tasks are beeing added by a trigger within the project. The assignee is set by default within the template. And the assignee is set correctly & completly, but the rule is not working for all the Tasks. “Allow this rule to be triggered by other rules” is also set.
@Tim_Schumann - are you using role-based assignment in your project templates? Or are assignees hardcoded in the templates? If it’s the latter, is there a reason you’re using this rule to multi-home the tasks instead of doing it in on the tasks in the template?
Since your rule works when triggered manually (I assume this means when you go in and change the assignee on a task instead of having the template set it), you could try adding another trigger for task added to this project.
I’m guessing (not 100% sure) the issue is that the way you’re assigning (via a project template) isn’t triggering a task assigned event, since the task is created with an assignee already set.
