When using Parent Task as a column & field an error occurs during import. The Parent Task id has to be previously defined in the db.
With using a multi-tiered project & csv each tier will have to be broken up into a seperate csv and imported from the top level down. At each level the task id for the upper tier will have to be tracked and put in the next csv as the Parent Task for this to work as is.
There needs to be some more logic in the script to handle this and track the Issue IDs throughout the import and handle the linking the Parents correctly.
When using Parent Task as a column & field an error occurs during import. The Parent Task id has to be previously defined in the db.
With using a multi-tiered project & csv each tier will have to be broken up into a seperate csv and imported from the top level down. At each level the task id for the upper tier will have to be tracked and put in the next csv as the Parent Task for this to work as is.
There needs to be some more logic in the script to handle this and track the Issue IDs throughout the import and handle the linking the Parents correctly.