We have a request form that duplicates a blueprint. The blueprint has one parent task and lots of sub-tasks, all with dependencies set up so that all the task due dates adjust automatically based on values from the request form. Here's how it's currently set up.
The request form has a field for TODAY'S DATE (schedules the start date of the parent task and moves all dependent tasks to the same day) and a DEADLINE DATE field (schedules the end of the parent task which pushes the milestone to the correct date.
I would like to add logic to the form now so that some of the sub-tasks are assigned to a different person based on a specific value. For example, if it's a request for a community event, the highlighted tasks assign to Emily. If it's a partner request, it assigns to Ashtyn. I seem to be hitting roadblocks at every turn.
I tried duplicating every single task I wanted to assign dynamically and adding this to the form:
It gets a little messy because the blueprint has so many tasks, but I thought it could work:
However, assigning sub-tasks using logic in the form means that they're not built out as sub-tasks to begin with. So it breaks all of the dependencies and the tasks don't line up anymore:
(Illustrating no parent task):
(Illustrating result with no dependencies):
I don't want to create multiple request forms.
I wish you could just use the field logic to change which PARENT task is created instead of just adding the sub-tasks. Seems like a pretty big limitation.
TLDR: Does anyone have ideas on how I can dynamically assign users to sub-tasks using a form field while keeping dependencies intact from the blueprint?