Table of Contents
A task is a small piece of work which involves changing files to a version of the project. As a rule of thumb a task should take no longer than half a day to complete. Otherwise you should create a feature and break the work down into smaller chunks which get created as tasks within the feature.
You can view the tasks for all projects, an individual project, a project version or a version feature in the Projects view as described in the section called “Projects View”.
Tasks can be assigned to the version in which they should be completed or can be left in the project backlog. The project backlog is a list of all the tasks which have not yet been assigned to a version. Assigning tasks to a version is described in the section called “Moving/Scheduling Tasks”. Tasks can be assigned to a user or group where they will appear in the My Tasks view. This is described in the User Guide 'My Tasks View' chapter.
PureCM is flexibile in how you use tasks. You could implement a 'top down' workflow where tasks are raised in the project backlog. A manager assigns the tasks to the version in which they should be implemented. A lead developer assigns the tasks to the developer. A developer can only submit changes against a task which has been assigned to him.
Alternatively, you could implement a 'bottom up' workflow where developers are free to create tasks against a specific release and assign them to themselves. You can specify that tasks are not required to submit changes. In practice you will probably adopt a workflow which is somewhere in the middle.
You should create your project and versions before woking with tasks as described in Chapter 2, Projects.