Project Templates

[#1]

Description - Today in Workfront, templates are used at the project level, but it would be great to see this ability at the task level or give users the ability to choose between several options

Why is this feature important to you - In my instance we use several templates within one project, but the way templates are today it becomes an issue for reporting and editing. We've run into several issues that cause us to change an entire process due to the templates being more associated with projects than tasks.

How would you like the feature to work - Admins should be able to choose how to use templates 

Current Behaviour - Templates are project templates 

[#2]

I'm a little confused on this - templates are a defined culmination of tasks to be used in projects, that is the intention. What are you envisioning for a task template since a task is only 1 object/piece of the project? You can include custom forms on any tasks within your template tasks, not just project-level custom forms, is that what you need?

[#3]

So templates are created to be used as project templates so one template per project, but as a marketing team we have campaigns that may consist of several templates to make up the campaign. We do not open a new project for each part of the campaign we create one project and attach several templates, but this can be difficult because the settings on templates are all at the project level (custom forms included) so we have become a little creative to get around this but it causes several issues. 

[#4]

Are you create a project using a template, you are able to add in multiple other templates into the project as well (it is common for orgs to have modular templates to piece together in a single project as needed). If you click next to the 3 dots next to your project name, click Attach Template and go from there. It'll add that template's tasks to the bottom of your existing project but you can adjust order as needed. is this what you're looking for?

[#5]

I'm not sure if this will be helpful for you or not, but we have some templates built for the purpose of starting a project and those used to attach to an already existing project. 
Those that are used for starting (or converting an issue into a project) have portfolios, programs, custom forms and tasks preset. Those templates have the word "development" within them.

When a specific process/workflow (set of tasks only) needs to be added within an already existing project, a template that we call "attachment templates" are used. These templates do not have portfolio, program or custom forms specific to the project preset within them. These templates have the word "attachment" within them. We also start the name with "Z" so they are at the bottom of template selections to help them stand out as attachment only templates. They are never used to start a project, only to attach to an already existing one. We use these for repeatable processes/workflows with an existing project.

Again, not sure if that's what you were meaning or thinking, but maybe it helps.