Task is not multihomed when project is created from project template

English Forum Ask the Community
,
1

My client has a project template where one of the tasks is multihomed with project called A.
When we use this template to create new project and this operation is done by:
(1) person who has access to project A, the task in newly created project from template is multihomed as it was designed in the project template,
(2) person who do not have access to project A, multihome is broken and we have to fix it manually.

Is this correct behavior in the case (2)? If yes, is there any workaround that helps us not to fix this multihome manually? Now we have inconsistent results depending on who is creating the project from template.

Here are some screenshots:
a) task in the template

image
image532Ă—527 19.3 KB

b) task in the project from template

image
image657Ă—493 18 KB

2

I did an additional test.
I added this person to the project A as a viewer. Now he can see the project A name in the task in project template. But once he creates the project from template, the task is not multihomed. I assume that editor role will fix this issue, but it is not acceptable.

3

@AnnaPapiernik,

This is expected behavior, I’m afraid, and I believe it has to be so in order to enforce privacy/access rights.

Workarounds would be to:

  • make your access rights looser to ensure those creating projects from the template have the required access, or
  • restrict who can create projects from the template to those who have the required access rights.
  • remove the multi-homing specifications from the template and replace with a “Setup” task assigned to someone with the needed rights to do this after project creation. You’d want to “mark” the tasks that need this treatment, perhaps with a custom field or otherwise.

Thanks,

Larry

4

Larry,
Thank you for your comment. I considered the same workarounds.

I know that in my case (2) this person has no edits right in the project A and this is the reason of the issue we observe. But still if multihome is fixed by another person, the one who created project won’t have access to project A so privacy of that project is secured.
I suppose that this behavior is not sth we could discuss with Asana.
But it would be great to have at least some notification that the project is not fully setup because of access rights (or sth else), when the creation of the project is completed. Then we could discover the issue during testing and implement other solution.