Tasks are the backbone of WeTrack. They are flexible in terms of what exactly they represent and their content, but essentially they are items of work that must be accomplished in order for a Project to be complete.
Tasks belong to a Project, and in that project are organized into Task Groups. Users can create identical tasks in different Task Groups and Projects, but they are separate entities that are identifiable by their specific Task Group and Project context.
Tasks have multiple ways to assign responsibility and visibility:
- Tasks can have an Owner, whose responsibility it is to see that Task completed.
- Tasks can be specific to a certain Department or the shared responsibility of many Departments; if tasks belong to multiple departments, we recommend designating a primary department.
- User Groups can also be associated with tasks. User Groups are custom groups of users who should own or have items shared with them; often these users are in different departments.
Tasks have a Start Date and a Due Date to facilitate scheduling. The original start and due dates become Baseline Dates, which are used as a reference in case start and due dates are then changed, allowing you to see how far before or after the original dates you are.
Tasks can have dependencies so that you know that you can't start a task until another one is complete, or that this task is holding up progress on another task.
Tasks have a RAG Status (Not Started, Slipped, Slipping, On Track, or Complete) so that their progress can be monitored and any problems made known.
For instructions about creating tasks, see Add Tasks and Milestones.
About Sub-Tasks
Tasks can be broken down into sub-tasks, which are the component pieces of work that make up a task. For the parent task to be deemed complete, all of the sub-tasks must be complete.
Sub-tasks are viewed Task and are also visible on the Gantt chart.
Sub-tasks also have owners, departments, user groups, start and due dates, and RAG status. Not all features/information on tasks is available on sub-tasks; for examples, sub-tasks cannot be tagged.
Updating the RAG status of sub-tasks will cause the status of the task to updated; parent task RAG status works on the same aggregation process as Project and Department RAG statuses. See Automatic RAG Status Calculation for Projects, Task Groups, Tasks, and Departments for details of task and sub-task RAG status interaction.
For instructions about creating sub-tasks, see Add a Sub-Task.