Hi community! My company just wrapped up a Professional Services engagement with Asana where our rep helped us build out 20+ different marketing project types (email campaign, poster, blog, etc.) that will launch when someone submits a corresponding request form. Because of the different variables the form and subsequent project it launches needed to capture, our Asana rep used a subtask configuration to spin up projects with specific tasks that match the form variables (e.g., if someone indicates in the form that they need the copy team to draft the content for an email campaign, a certain set of subtasks get assigned to the copy team in the project that’s created).
Since each request type (e.g., email, blog, landing page) has different configurations with subtasks that populate based on combinations of different conditions, I’m using branch duplication frequently to create the different project configurations for each request type, once I have my robust configuration built. This lets me carry over all the dependencies, team planning boards, durations, etc. for each of the tasks that make up the project, without having to do each configuration from scratch.
My issue: when I try to duplicate my branches so I can customize conditions and tasks for the new configuration, several of the custom fields won’t carry over. I’ve been told by Asana support that it’s because many of the tasks I’m duplicating in the branch are subtasks, but I believe our Asana rep did this successfully for several of our request types. Have others been able to do this successfully?
I’ve seen some similar posts, but I’m not clear if those OPs are using the same type of “form submission > project creation” subtask rule configuration that I am. Any help would be appreciated. I really don’t want to manually add 2-4 custom fields for 20 tasks across 15 different configurations if I can help it. Thanks in advance!