The recently introduced Custom Task Types & Statuses are fantastic but I find them limiting with regards to universal dashboards or portfolio dashboards because each custom type is unique to a project and cannot be quantified globally.
I’m hoping a fast follow will be to add support for custom task types in Bundles which would resolve these initial shortcomings.
This is similar but different to:
Agreed! We love the new custom task types and also want a way to roll them out without rebuilding for each project.
Important request, @Richard_Sather; voted. Thanks!
I agree. Right now I have a dropdown field for task status that’s included in a bundle and applied to all projects. I think the new custom statuses are interesting, I always wondered why there wasn’t a built in status option beyond complete/incomplete. But we use consistent statuses across all projects and I can’t build this into every project individually.
Agreed - needs to be org-wide to be useful in dashboards, common workflows, etc.
Huge +1! For me (and I’m assuming basically anyone at a large org), custom task types aren’t really useful until they’re supported in bundles (and project templates), as one of the key value-adds would be workflow standardization and reporting across many projects.
Post replaced with this Topic.
@Aj_D I replied to that post, but also, if you haven’t yet, be sure to add your vote here!
Agreed Richard, we will quickly adapt how bundles are rolled out if we can incorporate this into them. Added a vote to this one 
+1 here, highly useful to bundle. Would definitely help migrate those slightly older projects that have bundles attached to new custom task standards.
Hi @Peter_Louie , thanks for adding your voice to this.
To make your +1 count, make sure to scroll to the top of this thread and click on the Vote button in the top left 
It’ll be actually great if Custom task types were gathered in some kind of library. We have many different projects that need to use the same task type, and changing it once and for all of them, would be nice
Not to be a party pooper, but unfortunately I doubt this request is something that Asana can fulfill anytime soon; in order to do it, they would have to completely change the way custom task types are stored and handled in the underlying data model, which is currently strictly on a per-project basis.
It’s not sufficient just to add them to a task template in a bundle, because when a task template gets promulgated into a project from a bundle, it becomes a new and unique task template, unrelated to any others in other projects the workspace. If a custom type were supported in such a task template, when promulgated it would become a new and unique custom type unrelated to those in other projects, but would have the same name - that IMO would be incredibly confusing and thus even worse than the current situation!
Hi @Phil_Seeman , I understand your point. Having experimented with custom types, since I posted this request, I’ve understood that they are a subtype that can actually be applied to several task templates. I initially thought it could only be used in one task template and thus the request being tied to bundles.
With your feedback and having experimented with the API and understanding the subtype structure, I don’t see why we could not have a custom type library so that custom types can be global objects, that are optionally attached (this is the key) to a task template? We have three global task types today, available in all projects: tasks, milestones and approvals. I think the ask would be to increase the list by having an ‘add from library’ option, similarly to fields.
Now I’m stumped whether to change the title of this request (which perhaps the 49 voters may agree/disagree with) or create a new request for ‘Custom task types to be globally available in a library, applicable to multiple projects’ or something along those lines.
What do you think, @Phil_Seeman ?
How does that work?
Whether they are stored in a library or not, it’d still be handy to have them available in a bundle, wouldn’t it?
Maybe create a separate request and cross reference as it might serve as a stepping stone?
Create a task template A and apply task type X.
Create a task template B and you can also apply task type X (because it is bound to the project)
Agreed, definitely useful in a Bundle. But task types do not need Bundles in order to be global, just like custom fields do not need to be in a bundle to be global, but certainly useful that they can be added to a bundle. The same logic could be applied to task types - they should be available from a library and used in Bundles as well as Rules & Task templates that can create such task types.
Done, and added to the OP:
I think you made the right call to create a new thread.