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 have been completed.

Sub-Tasks can only be created once the parent Task has been created. They have much of the same attributes as Tasks, albeit with slightly less functionality. They can still be allocated RAG Statuses as they still have the potential to affect the overall outcome of the Project.

Sub-Tasks can be found in the second half of a task’s details page. Here you can add new sub-tasks, and click into a sub-task for fuller detail about it – in much the same way as a task details page.

Logic behind sub-tasks

Updating the RAGs of Sub-Tasks will cause the RAG of the Task in which they sit to be updated: "parent" Task RAG status works on the same aggregation process as Project and Department RAGs. However, if you update the RAG of a "parent" Task directly, the same RAG will be automatically applied to all of its "children" Sub-Tasks. The exception to this is sub-tasks that have been already marked as complete, which would never be automatically changed to a different RAG.

Did this answer your question?