As consultants helping clients on a daily basis, it was important for us to understand what V2 actually brings, but more importantly what will be lost when the migration is forced upon us!
This post is about what we lost between project template V1 and V2. âSaved Viewsâ and the âHideâ button did not exist at the time, so we did not lose them. Not being able to use them is more of a Asana, show me your BUTs đ
Everything that V2 offers that V1 did not have
Tasks assigned in project templates will no longer show in the assigneeâs My Tasks.
Due dates are relative and are based on the project start or end dates, no need to define âfake-realâ dates anymore.
Ability to define project memberships separately from the template edit access
All templates related to a team can be found on the team homepage
Ability to convert a task to a template using a project template.
Templates donât clutter the sidenav because they are no longer a real project
Ability to add a project to portfolios automatically
Everything that we lose when moving to V2 The list was double-checked on September 11th 2022.
No way to go back to V1
No apps/integrations available.
No ability to define color and icon for the projects
No ability to sort/order templates on the Team homepage
No ability to duplicate a template
No ability to multi-select tasks and apply bulk actions
No ability to choose sort and filter options
No ability to share a task between templates, or between a project and a template
No ability to define a dashboard
A task canât be recurring
Full Overview tab is not be carried over into the new project. (only the notes are)
[api] No CRUD (create-read-update-delete) capability for PT 2.0, so no ability to do things like read the tasks in the template, get or set custom field settings or sections, etc.
[api] Workspace-level webhooks do not generate events for the creation or updating of PT 2.0.
No access (read, edit) from mobile app.
Cannot put comments on the template tasks (for the purpose of explaining the template)
Canât expand task and see its subtasks from the editor
Dependent tasks do not show the hourglass icon
[api] No longer able to pick and choose fields to include/exclude when using a template
No icon indicator that a task has subtasks.
Cannot be placed itself into a portfolio
Canât move a task into another task to create a subtask
No ability to duplicate a task 23. No ability to define task templates
No timeline view to help with creating the structure
No ability to create dependencies with tasks outside the template
No ability to find tasks in template through search (but you can now find the template itself)
No ability to create a project with no project start or due date
Completed tasks donât get carried over into a template
No ability to add a subtask to the same project template together with parent task
No ability to use a task template to create tasks within the template
The second list has some serious topics: losing dashboard or recurring tasks will surely break some workflows⌠Anyone else hopes Asana would delay the migration?
Let me know if the list is inaccurate or incomplete! @ambforumleader
Here are two API/programming items for the âEverything that we lose when moving to V2â list:
No CRUD (create-read-update-delete) capability for PT 2.0, so no ability to do things like read the tasks in the template, get or set custom field settings or sections, etc.
Workspace-level webhooks do not generate events for the creation or updating of PT 2.0.
It sounds like #1 in what V2 offers should be in the loss area. Tasks assigned wonât show in My Tasks?
This sounds like a basic function. How will the assignee know what to do?
Great list. As Iâve been testing the v2
Templates (and after reading this list), Iâve realized weâve lost way more than we gained. Pretty concerned about our org being forced to make the change.
Another loss Iâve encountered is the ability to see the subtask dropdown in âEdit templateâ. It may seem small, but being required to click into the details of each task to view/edit the subtask is a big gap for my use-case. The extra seconds the extra click(s) require to edit subtasks in the template add up.
Previously with the project duplicate API you could specify which data to include when duplicating. One of those being the task collaborators.
With the new Project Template instantiateProject API, I donât see a way to exclude the collaborators of the tasks in the template (other than not including any collaborators on any of the tasks within template itself).
Another example is whether or not to include the project (now template) description. By default, it now adds it with the API (which is fine with me). But previously we were able to exclude the notes from the body data.
We hear you and have plans to address most of these pain points with upcoming updates! Make sure to keep an eye on Product Updates in the coming weeks/months
I am not seeing a way to copy a task from a project to an existing template; I would normally duplicate the task & move it into the template but I donât see how to do that now.
The mobile app indeed wonât allow you to read or edit a template, while youâll still be able to do so from the web version. Asana is working on fixing all those limitations, we donât know which one will be fixed and when.
We are pretty certain all of the shortcomings will be added in at some point, so I would suggest a re-wording of your question:
Who decides what subset of previous features is an acceptable amount to release a replacement?
I would argue, and I think most here would agree, that PT 2.0 was released with too-small a set of features and should have been delayed until more of them were built into the replacement.
This post is about what we lost between project template V1 and V2. âSaved Viewsâ and the âHideâ button did not exist at the time, so we did not lose them. Not being able to use them is more of a Asana, show me your BUTs đ
Everything that V2 offers that V1 did not have
Everything that we lose when moving to V2
The list was double-checked on September 11th 2022.
