New CSV importer: dependant tasks should be listed below their parent task

On “Set dependencies between tasks”, it doesn’t make sense to have dependent tasks located above the current row in the CSV file because you would naturally list the tasks in order of date so dependent tasks would come after the task that they are dependent on?

1 Like

I agree with you @Joanna_Yiptatchung and the Guide seems to read as though it works opposite of how you describe.

Hi @Joanna_Yiptatchung and @Jerod_Hillard,

I’ve gone ahead and moved your comment into a new #productfeedback feedback thread to allow other users to share their thoughts and vote on this topic too. I guess that due to technical reasons, we need the dependant task to exist (=to be imported) before we can create a dependency. Sos not sure if this is technically possible the way the CSV is currently built, but I’ll make sure to keep you posted as soon as I have some updates!

1 Like

@Marie thank you! It makes total sense that the dependent task needs to be created to map a dependency. Why not use the Dependents column to list the “task that the current row is dependent on” instead of “the tasks that are dependent on the current row”. By doing so, both tasks would already have been created via import.

Typically you would list tasks in chronological order so “do this” would show before “then do this” when perhaps “then do this” is dependent on “do this”


2 posts were split to a new topic: Issue with dependencies during CSV import