New to Asana and adding my voice. This is something that we had in previous project management software systems, and I am very surprised that Asana lacks it. 
Hoping for update soon here as we are rolling this program out to our team. Concerning that the community has consistently been asking for this for years with no updates or result.
It’s incredibly frustrating that Asana’s “new” template system was launched without feature parity — and even more frustrating that three years later, it’s still not fixed.
We have a template created by someone who left the company years ago. It uses roles (as intended), but now we’re stuck — there’s no way to transfer ownership of the template, and deleting the user only reassigns tasks and projects, not templates. I can’t even duplicate the template without losing all the roles, which completely defeats the purpose.
The lack of basic administrative control over templates is a serious oversight. It’s disappointing to see this has remained unresolved for years, with no clear path forward. This isn’t an edge case — it’s a common lifecycle issue for any growing organization.
Please prioritize fixing this. At minimum, we need:
- A way to transfer template ownership
- A way to duplicate templates without losing roles
- Admin visibility and control over all templates in a workspace
Three years is too long to wait for parity on core functionality.
3 Likes
@David_Russell - sorry you’re having issues (I definitely sympathize on the admin front…). For your specific case, you should contact support and they should be able to re-assign ownership of the template to you (obv this is not a long-term fix).
Keeping this thread alive and kicking (unlike template duplication which remains awol )
Another +1 for this feature. This is absolutely CRITICAL!
How is this not an option yet? Ridiculous.
Is there seriously no way to do this? OMG I will spend hours duplicating one from scratch, and I can find no help on this.
Welcome, @Carolyn_Kanon,
I’ve merged your post into an existing topic where you can click the title to scroll to the top and vote by clicking the Vote button.
Thanks,
Larry
How are we in 2025 with no solution. This is basic functionality. Must be added.
@Garrett_Knoll we need you 
#batman
1 Like
Adding my up vote to this long list of frustrated Asana users who need a true solution for template duplication.
Adding my voice to this. Can’t believe the capability to do this in a simple way doesn’t already exist.
1 Like
@Bastien_Siebman Bat-Signal received! The team owning Project Templates is currently prioritizing supporting saved views in templates (something I’ve fought for for awhile!). We hear you all and appreciate the patience, but this is not quite in our current roadmap. I’ll be sure to keep you all updated though 
4 Likes
Not if you’re trying to create different, but similar templates. For example, a project template where you have a long-lead timeline and a project template for a short-lead timeline and both require the same tasks but with different due date automations. Or for projects that are similar but of different scales – you can duplicate the template and then fine tune it to fit the different project scales without having to create each template from scratch.
Welcome, @Shayna_Brodnick,
An approach I recommend to clients who use it effectively is to try, if possible, to make a single template work for the different permutations.
It might require a setup step or two (I include these in the template too so it becomes self-documenting) upon instantiation of the project from the template for the non-default, most common case. For complex and simpler project types, I try to structure the template so sections and tasks can be deleted easily. You can “mark” them with a single-select custom field with values that correspond to the non-default project type(s).
Similarly, you could trigger a different rule than the standard one for non-default project types.
Thanks,
Larry
This duplicates the tasks, requiring changing multiple templates if the core process changes.
This runs into the same issue.
Redundancy - other than for backup purposes - is one of the primary reasons for error in modern knowledge work.
It starts off with one duplication, and someone thinking “Oh, I just need to not forget to update the other template when things change”
Then that gets duplicated, and people end up with 14 templates, each slightly different for that specific client/situation.
Everywhere I worked where I saw redundancy it eventually led to errors, and a quest to make sense of the variations.
Not only does this introduce errors into your process, it also introduces a resistance to change, because changing the core process now require changing it in 14 places rather than one.
But the improvements you can make for the work that are the same across all variations are most impactful for improvement, as they impact all of your variations.
This is why I - as an improvement professional - oppose duplication of templates. Because my job often involves preventing and reverting redundancy.
I’d take @lpb’s approach any day over duplicating a template.
@Garrett_Knoll I’m hoping you/the team takes this into consideration when considering this request vs supporting Modular Templates, which in my opinion is extremely underrated compared to this thread. It may not be the feature everyone wants, but I think it’s the feature people actually would be better off with.
1 Like
I am disheartened to hear that 2+ years into the community asking, this isn’t even on the roadmap.
When are we going to be able to duplicate templates for real?
@Garrett_Knoll This feels like a basic feature that should have been implemented years ago. It’s strange to me that this feature isn’t even on the current roadmap. Especially considering how many users have asked for it, as well as the length of time that has passed since the start of this forum.