Just like custom fields added to a library, it would be great to add custom task types to a library so that they are standardized and available to add to any project.
That way, the project that the task type is multi-homed could be grouped by that task type and other features such as rules could be used in that multi-homed project. Additionally, they could be quantified in global Dashboards. This would really expand the usability of custom task types which currently are great if they are isolated to one project - not ideal.
We have a fairly complicated series of rules set up to run Agile projects in Asana. Seeing the obvious benefits of Custom Task Types, I wanted to rebuild that system. Without CTT being added as Library items or Bundle items, it’s a complete no-go.
We’ve heard your feedback loud and clear, our top request for custom task types was: “I spent a bunch of time creating a custom task type in my project, only to find out later that I can’t use it in another project.” Well, that changes today!
I’m happy to announce this feature is now available on all paid plans. Here’s what you can now do:
Share custom task types with others: Give specific people access to your carefully crafted task types through our new sharing controls
Add shared task types to any project: Use the Customize menu’s new typeahead search to find and add task types you have access to.
Access task types independently: No need to rely on task templates anymore, use task types on their own!
This means if your marketing team creates the perfect “Campaign Brief” task type, they can share it with the design team, who can then add it to their own projects. Everyone stays aligned with the same structure and workflow! Thanks all for sharing your feedback on this thread!
As @Phil_Seeman discovered in early testing, this statement is only true if the task type is set as the default task type of a project, which is not very intuitive.
This is great, but a caveat with custom task types: They’re not supported in Advanced search, so be very sure your workflow can withstand not having that fallback.
@Bryan_TeamKickstart , until that is a available, my workaround is to create a (temporary) rule to trigger manually, mapping all status field options to a task type option, selecting and applying to 50 tasks at a time.
Just watch you don’t trigger any other rules in the process! Ideally, migrate to task types first, then remap rules.
Thanks all for sharing your feedback on this thread!
