Auto-Fill Date Ranges for Manually Added Task/Subtask Dependencies

English Forum Product Feedback
, ,
1

Hello. In many cases, our team is having to manually add date ranges for a subtask that is not known at the time of subtask creation (design package start dates in our case). The dependencies are set up and the estimated times are input for the remaining subtasks using a workflow/task template, but when you add a date range into the first subtask that kicks off the process, it does not auto-fill the remaining subtasks with date ranges and we have to manually add date ranges for each subtask every single time.

I know that you are able to get tasks to populate by creating a Project template, but as mentioned, most of our projects don’t have a set “start date” therefore we cannot approach it that way. I’d like to see if we can incorporate this auto-fill of due date no matter the situation as long as there is a dependency and estimated time setup.

I can give access to a current project I have setup for reference or can share my screen and walk through with someone to help explain better.

2

Hi @Sean_Gutierrez , you may want to try using a rule to create your subtasks which can be dependant on each other like your task template.
But, unlike task templates which trigger dates from ‘today’ only, the create subtask rule can leverage variables such as the due date or any other date field which you could use as an operator to offset your start date and therefore set all subsequent subtasks dates and durations.

I usually do a better job explaining all this during a live online engagement, which is what I do as an consultant. :slight_smile:

Hope this helps!