Creating Tasks and Subtasks in Wrike via XLS Import
All users (except for collaborators) can import tasks, folders, and projects from XLS files into Wrike. To create a task in Wrike, using XLS import you have to add data about the task to the Excel file.
You have to format your file according to guidelines here or download a sample file from Wrike and add data there.
Adding a task in Excel is easy. Just enter the task title in the “Title” column. Then use the other columns to enter any additional information you'd like to specify about the task.
If you'd like to create your task within a folder, first create the folder and then add the task in a row immediately beneath the folder's row.
Add start and end dates for the tasks using the slash symbol as a separator (e.g., 23/10/2019). The duration is calculated automatically, based on start and end dates. The end date is calculated automatically when you add the start date and duration. If the start and end dates are in place and you manually add the duration, which is more than the automatically calculated duration, the end date will be shifted after the import and will be adjusted to fit the duration.
To create a milestone task, enter the task title in the “Title” column. Add a date in the "End Date" column, but leave the "Start Date" column empty. Then use the other columns to enter any additional information about the task.
Add your description in the “Description” field. Data entered there is added to the description section of the task in Wrike.
Add a status to a task by typing one of the default statuses in a task’s “Custom Status” column and adding the status group name (Active, Completed, Deferred, and Cancelled) to the "Status" column. For accounts created before December 12, 2016, the default statuses are: Active, Completed, Deferred, and Canceled. For accounts created after that date, the default statuses are: New, In Progress, On Hold, Completed, and Canceled.
Business and Enterprise users have the option to add a custom status to a task. First, go to the task row where you'd like to add the custom status, type in the custom workflow’s name in the “Workflow” column, and then type the desired status in the “Custom Status” column. If the custom status or workflow can't be found upon import, then a status from the default workflow will be applied.
Data in the "Workflow" and "Custom Status" columns is case sensitive.
To include a task in several folders, begin by adding your task to one folder. Then, to include the task in an additional folder, simply copy the entire row with the task information (including the key number) and paste it beneath another folder.
Add data as you normally would for a task and then add the parent task's name in the "Parent Task" column. The parent task must appear in the file before the subtask.
To create a subtask of the subtask, the entire task path has to be specified in the “Parent task” column.
To perform XLS import, the parent task and subtask can't have the same name. There should be at least one symbol of difference.
A dependency between two tasks can be created by using the “Depends On” column. Go to the row of the task for which you'd like to add a dependency and, in the “Depends On” column, enter the key number of the task on which the current task will be dependent. In the same cell (without any spaces) add one of our dependency codes. For example, your “Depends On” cell might look like this: 5FS. If you want to add several dependencies, separate them using a comma and space (e.g., 22SS, 32FS). Lastly, add start and end dates for the task in the appropriate columns (or only an end date if the task is a milestone).
Upon import to Wrike, dependent tasks are automatically rescheduled to start as early as possible without breaking the dependencies. However, you can delay some dependent tasks by specifying their preferred start dates in the start date constraints column. Dependencies don't affect dates of milestones, and if the dependency that includes a milestone causes a conflict, it'll be highlighted in red on the Gantt chart after the import.
Accepted dependency codes:
FS — the dependent task starts when the predecessor task finishes.
SS — the dependent task starts when the predecessor task starts.
FF — the dependent task finishes when the predecessor task finishes.
SF — the dependent task finishes when the predecessor task starts.
Start to start (SS) and start to finish (SF) dependencies aren't applicable to milestones.