Expand my Community achievements bar.

Do you have questions about the migration to Adobe Business Platform? Come join our upcoming coffee break and ask away!

Allow custom forms to be excluded when attaching a template to a project

Avatar

Level 7

12/14/22

We need the ability to exclude custom forms when attaching a template to an existing project.

 

Currently, when you attach a template to an existing project, it forces you to include all custom forms associated with that template. This means filling out the required fields just to attach the tasks you need. In some cases, the current behavior has also caused us to go over the limit of the number of custom forms we can have on one project.

 

Our PMs regularly need to attach new tasks when the project scope changes, or if work needs to be redone. Their current workaround is to create a fake project from the template they would like to use, then copy over the tasks from the fake project to the actual project. Copying tasks from similar active projects does not work and causes issues with inherited permissions/notifications. So, the only workaround they have now is very cumbersome. 

 

2 Comments

Avatar

12/14/22

We have a workaround of what we call "attachment templates." They are project templates that do not have any custom form on them and they have the word "attachment" within their name so they are easily identified as templates that are meant to only be attached to existing projects. They are not used to create projects, only attached to existing ones. Just an idea to consider that works for us.