I am working on a project that has a rule that converts a task into a project upon a certain trigger.
The project is created from a template where some of the tasks are multihomed in several projects.
When these new projects are created from the rule, the tasks that should be multihomed are only in the newly created project.
When I manually create a project using that same template, the tasks are correctly multihomed.
Is this a bug or the expected behavior? If it’s the latter, why?
I’d say you should report this as a bug (and thanks for the very clear description which would be great for Support to understand).
While it’s true there are a couple of differences between a task conversion to project by rule vs manual, this should not be one of them, I feel!!
Try these troubleshooting steps, then please create a support ticket: see How to contact our Support Team.
Thanks,
Larry
1 Like
@David_Jane, can you confirm if the projects tasks are multi-homed in are public or private to members? If they’re private to members, I believe this might be expected:
-
When you manually create a project using this template, Asana knows you have access to projects tasks are multihomed in, so it’s automatically multihoming these tasks.
-
However when automations are creating these projects, they don’t technically on behalf of who they’re creating it, and therefore not multihoming tasks into private project?
That’s just a guess but I’m curious to hear what you think!
Hi @Marie , the projects where tasks are multi-homed are public.
I tried with Projects that are on the same Team, and different Team, and tasks are not multi-homed in any of them.
Hmm! Can you please forward a screencast to our support team, as well as screenshots showing your rule set up? Hope this gets resolved soon!
Sure, here it is:
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.