Tasks are all about tracking what’s been done and what needs to be done.
Now that you know what the project is about, and you’re up to date with all the latest information, you need to know what to do. This is where tasks come in. Tasks are essentially TODO lists, where you can:
- Create, edit, delete and complete tasks
- Assign tasks to users and see tasks assigned to you
- Create nested lists where each sub lists is a large task, which needs to be broken into sub pieces to be tackled efficiently.
- Un-complete tasks in case they weren’t actually completed
- View when a task and list was completed and by whom
- Set priorities for tasks, so you can see at a glance what needs to be done as soon as possible
- Categorise lists of tasks, such as the type of work involved, the stage of the project etc
- Comment on tasks
- Track time spent on a task
- Search your tasks, completed and pending
You will also be able to link tasks to other resources, so if a task is created in response to a ticket, you can see the ticket alongside the task, or if the task involves working on a file, the file can be linked to the task, so you have all the required resources rto hand when you begin working on a task.
One of the things I’ve found lacking in all project management is task types and task forms. What I’ve been thinking through is json formats for task flows.
Most “tasks” and task flows are really just blogs and threads with free text notes. Not conducive to anything but chaos.
With task types and forms you can load the form type and edit in a concise format.