Saved view tabs to be supported in Project templates

[Lone_Werner]

much needed !

[Tina_Pachl]

It’s been over a year since Saved View Tabs were introduced, a most excellent feature. However, as someone else mentioned, when using Asana for Agile you have to recreate the columns for every single Sprint. Is that not the purpose of the templates? Asana presents itself as oh so Agile friendly while overlooking the manual intervention needed. Please add the Saved View Tabs to the templates!!!

[lpb]

@Tina_Pachl,

I usually recommend to clients a very different approach for sprints that works well with the existing Asana feature set:

Ongoing Processes: *Current* Project, Aging, and Archiving Best Practices

Do you annually recreate some projects so you can update for the new year, like 2023 Marketing Requests? Or even worse, frequently recreate monthly or weekly projects, for example, Week 24 Dev Sprint? Stop that! (I’ll explain . . .) For ongoing process projects, like a marketing or operation team’s workstream, where work flows in, is actioned, then completed only to be replaced by more work, there’s a simple tweak you can make to simplify and clarify. Just recast that project instead as “ever…

Maybe it’s an option for your team?

Thanks,

Larry

[Tina_Pachl]

Thanks, I’ll check it out.

[Cyrill]

Please add these functionalities to project templates. I really find it hard to persuade my team to use templates when they still need to adjust the view of their newly created projects. This limitation defeats the purpose of project templates in my opinion.

[Nicolas_VIGNERO]

Dear all,

We’re experimenting with the use of Asana templates to standardise the management of our projects. In this respect, we’ve noticed that the Asana template doesn’t allow us to retrieve view tabs based on filters from the List view that we’ve added to our standards.

To compensate for this, we decided not to use the Asana template but rather a project that we named template and that we duplicate each time we start a project. This method allows us to retrieve a lot of elements.

The disadvantage of this method is that we lose the ability to use the automation process based on the action ‘Convert a task into a project based on a template’.

Are there any plans to enable the retrieval of filter-based views in the Asana template function in the roadmap?

Best regards

[Jan-Rienk]

Hi @Nicolas_VIGNERO,

I’ve added your feedback to this existing thread. Any votes have been transferred.

[Joseph_Hutt1]

I only just realized that this wasn’t a thing yet XD Makes the template a little less of a template Hopefully we see this come to fruition!

[Jeremy_Lee_Bradford]

Why is this even a thing? A template is just that, a template. If you create a template to be utilized, then everything that you create should be able to be utilized in said template. If you cant, then you don’t have a usable template and you might as well create a new project every time since you are having to recreate everything, such as the views, anyways. I have been having to use a blank project built out the way i need it and save it with the name “template”, not AS a template, so that I can use the views. And how many up votes does this need in order to get the traction its needs?

[Bastien_Siebman]

What might be happening here is that different teams of engineers are taking care of project templates and templates. Or this is the same team but the technical objects are different. Asana decides to make projects move faster than templates. This can be argued for sure.

However if a single feature costs twice to be put in 2 places, I’d rather have them test and improve with projects, and then add to template once it is stable.

@Jeremy_Lee_Bradford

And how many up votes does this need in order to get the traction its needs?

There isn’t an actual number, we discuss it here 🦄 If Wishes Were Unicorns: Why Asana Might Not Have Implemented that Feature Request (and other thoughts about Asana feature development and product strategy)

[AlexUCR]

After putting so much effort in designing the Asana project template for our organisation, today I realised that all the tabs are not included in the template.
I absolutely cannot understand that.

I thought I can fix that by creating a bundle with corresponding tabs.
But bundles are not including tabs, as well.

So we have to create all the needed tabs with its view settings manually after creating a new project.

[Richard_Sather]

Hi @AlexUCR , yes it is unfortunate this feature is not yet available. The alternative would be to duplicate your project but then you loose out on Project Template features such as prepopulated dynamic roles and relative dates.

Btw, you may also want to vote on this, since you mentioned Bundles:

Saved view tabs supported in Bundles

Saved view tabs are awesome. But, currently, they cannot be set as ‘Controls’ within a Bundle so that saved view tabs can be predefined and applied instantly to projects within a Bundle’s control. Currently, you need to set up view tabs manually in each project since they are also not suported currently by Project Templates. Current workaround is to a create duplicate of a regular project, which unfortunately loses out on all the functionality of Project templates. Please add support for saved…

[AlexUCR]

Hi @Richard_Sather , thank you for the hint with duplicating a project.
This can be a workaround for me for some time.

But we want to automate creating projects with a trigger from SalesForce.
I don’t know the capabilities of this integration, and am not sure if the trigger can just create a project from a template, or can also duplicate a project.
That’s another topic, I think.

I voted on yout mentioned thread.
Only 8 votes so far

[Phil_Budd]

Im just adding to what I feel is an already much wanted feature of Asana,

To help migrate Asana in our business over 100+ users we need the ability to create custom project Templates with custom views based on specific team users groups.

Currently we have it set up as a work around to duplicate previous projects but we lose a huge amount of automation in this process, this is so we can have the custom views that are needed.
please can you confirm if this feature is on a future roadmap ideally within the next couple of months?
We are an organization that’s growing very fast and need this feature asap.

[Brittany_Robinson2]

High priority need. Like many, we’ve had to make “template” boards to keep the filters, sorts, and other needed customizations. Not only does this reduce automation capabilities (with our team needing hundreds of these projects), it puts the template at risk due to the increased likelihood of human error in the duplication process.

[Alex_Berger]

Brainwave: If we can’t add saved views to templates (yet ), is there any talk of adding dynamic project ‘roles’ to standard projects? This is the only major obstacle for my agency to make the ‘duplicate a ‘template’ project’ workaround a complete solution.
The reasoning/additional benefit for adding this functionality to standard projects is obvious: it would solve the ‘what if a team-member is replaced mid-project?’ problem.
Imagine if a project’s owner could just change the assignee of any project ‘role’ (in the Overview view) and then see it dynamically update all rules and tasks associated with the previous assignee.
Apologies if this idea is already in another thread (will search now).

[Bastien_Siebman]

You can have a dropdown called “roles” and for each task select the right role. Then switching for a role would mean filtering the project and multi-selecting/updating tasks

[Gareth_Ellmer]

Similarly, the project Status Update - currently have to design this along with views manually for every project. If these two things saved in the template it would be an enormous time-saver.

[Richard_Sather]

Hi @Gareth_Ellmer , yes that would definitely be useful! You can vote for that here:

Templates for project status updates

We use Asana to work on projects together with customers. Meaning: guest accounts are involved in the project. After each milestone in the project we do a status update. For some status updates we almost use the same text (project kick off, postcare, closing). It should be more efficient to have the possibility to create a template for these kind of updates. Now we need to copy/past from a text file.

[Michele_Campbell2]

I use the same master template for all of my projects, and create multiple List views with different custom fields visible and filtered for different functions. (Budget tab, tracking tab, Documents only tab, etc) At this time, I have to create each list view manually for each project. Is there a way to add additional tabs with the correct configurations to the project template? If not, is this a feature that could be added?