Task Template vs Duplicating a Task

[Stefanie_Epstein_Con]

What is the benefit of using a custom task template versus creating a task in your project that you use solely for duplication purposes?

My teammates have created a task in our project that’s labeled “TEMPLATE for XyzAbc” and duplicate it every time they need a new task for the purpose it’s designed for. I want to tell them that creating a task template is more efficient than duplicating an old task, but is it truly the better option? What are the benefits? These are the only ones I can think of:

1. CLUTTER — Having a task in your project that acts as a template adds clutter to the project.
2. MORE CLICKS — Every time you duplicate the task you have to check or uncheck what kinds of information (like assignees, attachments, subtasks, task description, etc.) from the original task you want to include in the new task, and that just adds more work / room for error.

[Richard_Sather]

Absolutely better to use task templates, @Stefanie_Epstein_Con .

Adding to your point 1, tasks in the project will also clutter your dashboard charts with wrong data, counting those ‘placeholder’ tasks that your team uses to duplicate.

Task templates can also carry attachments, collaborators and subtasks. And you can also set relative due dates so the created task will always have a due date relative to when the task was created.

You can have up to 50 tasks templates as an ‘a la carte’ menu when you click Add task anywhere in the project.

It’s a no brainer, use task templates instead of duplicating placeholder tasks!