Hi all!
I'd like to suggest some feedback regarding blueprint dependencies.
At the moment, we are forced to input a date range on tasks in order to have a dependency created to it or from it. Even if you are adding dependencies between tasks that don't have a start/due date, the system will automatically assign a 1 day duration by default.
The hurdle I am working with at the moment is blueprints that have tasks that require a certain order and dependencies between them, but don't have set durations because they can take an undetermined amount of time (usually flexible, usually take long). The example we are working through right now is for case studies which can take months to produce as there is a lot of back and forth with external clients, so certain tasks can be in progress for a while. There still needs, however, to be certain dependencies between tasks to establish an order.
It would be helpful for us to be able to choose whether we want to have dates or not when adding dependencies in situations like this, and perhaps in other use cases that the community might have. We cannot guarantee a date range due to the lack of consistency in durations on tasks, but would still love to add dependencies especially when it comes to certain automations we have when tasks are completed to be able to start the next one.
Hope this all makes sense!
