Skip to main content

Hi everyone, 

I’m setting up a project management base with dependencies between tasks. I have two questions: 

  1. In some cases, task 2 can begin before task 1 ends, but the completion of task 2 does depend on the completion of task 1. There will simply be some overlap in when both start (e.g. parts of task 2 can be started before task 1 begin, however until task 1 is completed, task 2 cannot be fully done). I have set up the dependency as Task 1 → depends on → task 2. However, this then shows up as an error: Task 1 begins before Task 2 ends. Is there a way around this?
  2. What happens when you have some dependencies in the same table that are predecessors and some that are successors? 

Thanks a lot in advance!

Hey ​@SarahVFRF!

Would you mind sending over a couple of screenshots of your current structure (fields and examples) of your Tasks table?

Also, could you further describe your automations (if any)?

Mike, Consultant @ Automatic Nation 


Hi ​@SarahVFRF  unfortunately Airtable dependencies logic means that task A needs to finish in order to start Task B. 

You would need to create a workaround using other logic.

An out of my head option would be having a task named Task A Start. This can be used as a the dependency and after that task is completed, you can have Task A execute and Task B Start.

The cons on this is that there will be 2 tasks for that one single task.
 


Hi ​@Mike_AutomaticN

I attached a screenshot of one of the projects I’m referring to, in Gantt view. As you can see, some of the tasks are happening in parallel but don’t have the same end date + depend on each other.

I’m very new to the platform, I’m not sure what you’re referring to re automations? 

Thanks ​@felipe-saucedo also, ideally I’d like to avoid breaking tasks down any further - I want to keep our view as clean and concise as possible. 

 


@SarahVFRF  I get what you are saying but I am afraid dependencies in Airtable only work with end and start

 So A needs to finish to unlock B