After creating the stories, all the key factors in a project have been touched, including lifecycle, resources, and stories. Now what you have to do is to do WBS (Work Breakdown Structure) for each story and generate all the tasks required to finish this story.
Notes: It is to finish all the tasks of the story, including but are not limited to design, development and test tasks.

1.Stories of a Project

• On the page of the story list, you can easily decompose a story to tasks.
• You can also check the number of tasks decomposed.
  

2. Decompose/break down a story

Click the Decompose button of a story to create tasks for it.

• You can choose the story to link when creating tasks.

• The link to the linked story can also be provided.

3. Multiple and child tasks

Since ZenTao 9.6+, multi-user task and child task have been added.

3.1 Multiple tasks

When creating a task, you can check "Multiple" in the Assignee column, if you want to assign this task to multiple team members. Once it is checked, a "Team" button will show for you to click and select your team.

When selecting a team and team members, fill in man-hours correspondently. You can drag the username to order it.

After you choose multiple assignees, the names will show in the Assignee column and the total man-hour will be calculated.

3.2 Child Tasks

Choose a task to create child task on the task list.

The page to add child tasks is batch create tasks page. Fill in the required fields and click Save.

Then you can check child tasks on the task list page. Click  to hide/show child tasks. The default setting is to show child tasks.

• After child tasks are created, the estimate, cost and left hours of the parent task is the subtotal of that of all child tasks.
• When creating a parent task, man-hour is set. After creating its child tasks, the total man-hour of child tasks will override that of the parent one.
• Multiple tasks and tasks done by multiple users, cannot have child tasks.

4. Notes

•  All the stories should be decomposed into tasks, including design, test, design, even machine procurement, and test environment deployment.
• The decomposition should be as small as possible. For example, a task can be finished within several man hours.
• If a task needs several members to finish, then it should be further decomposed.
• You can batch assign tasks, if the type of tasks is routine work. For example, a routine work is to ask every team member to write a project summary. In this case, you can select the type as routine work and then assign it to all team members.
• The type of tasks should be set carefully, since it will affect automatic calculations in development stories. We will explain this later.
• The tasks are best to be claimed voluntarily, since this will boost team members' enthusiasm to the utmost extent.