can't use custom task type status in any way in multi-homed project

Hi,

I am trying to use custom task type.
I have project A, created custom task template there with its own statuses.
Task is created using this template and multi-homed to project B.

In project A I am able to group, filter etc. as per this task status, I can use it in Dashboard as well.
In project B none of it works. Almost as the task type does not exist there although it is multihomed from its source project. I can still update its status, but that is about all I can do with it.

How can I link the two projects so that they can share the same task template with all its perks?

Is there any way the custom task types can be defined as global, similar to custom fields, and chosen from a central library? That would seem to me as the obvious solution.

Any tips?

1 Like

Hi @VladS and welcome to the forum,

No, (unfortunately IMO) Asana built custom task types to be local to a specific project - except that as you discovered, if a task with a custom type is multi-homed to another project, its custom type comes along with it into that other project. But it’s not actually available as a custom type in that project. I’m afraid there’s no way to have global custom task types or to have the task template be shared between the projects as you’re asking about.

Hi @VladS , additionally to @Phil_Seeman 's comment, the only way I can see task types becoming globally available is to have them supported in Bundles. If you agree, you may want to vote for this:

Yeah, unfortunately that request is really problematic - I just added a comment in that other thread to explain.

Thank you for your response.

If that is the case, then there is no use for them in my case. I need them to be carrying their properties to the other projects and be centrally controlled.

It looks very promising as a concept, but its execution and the fact that it is strictly project-based makes it unusable.

I have to re-think my strategy of building the project architecture :slightly_frowning_face: