Definition: A task in Taskade is a single line in a project. It is the basic unit of work, and it can hold subtasks, assignees, due dates, tags, custom fields, comments, and files. Every project view is a different way to look at the same tasks.
TL;DR: Press Enter to add a task and Tab to nest it as a subtask. Add assignees, due dates, tags, and custom fields to give it context. Because every view reads the same tasks, a change in the list shows on the board, table, calendar, and more. Build a task project free.
Why do tasks matter in 2026?
Work breaks into pieces, and each piece needs an owner, a date, and a place. A task that carries those details in one line is easier to trust than a note plus a separate tracker. Taskade tasks nest to any depth, so a large goal can break into steps without leaving the project. Since AI agents and automations read project data too, a well-kept task list is also the memory your automation acts on.
How do tasks work?
- Add. Click an empty line and type. Press Enter for the next task.
- Nest. Press Tab to indent a task into a subtask. Press Shift + Tab to move it back out.
- Detail. Add an assignee, a due date, tags, or custom fields.
- Discuss. Add comments and files to the task.
- View. Switch between universal views to see the same tasks as a board, table, calendar, or mind map.
What can a task hold?
| Part | What it does |
|---|---|
| Text | Names the work |
| Subtasks | Break the work into steps, nested as deep as you need |
| Assignee | Says who owns it |
| Due date | Places it on the calendar |
| Custom fields | Add status, budget, priority, or any data you track |
| Comments and files | Keep the discussion with the task |
A worked example
A studio creates the task "Launch the website". Under it go "Write the copy", "Design the landing page", and "Build the pages", with "Home" and "Pricing" nested one level deeper. The lead assigns each piece, sets due dates, and adds a Status field. The team reads the tree in List view, drags cards on the Board, and checks the Calendar for deadlines. All three views show the same tasks.
Common mistakes with tasks
- Making one huge task. Break it into subtasks so each has an owner and a date.
- Tracking status in the task text. Use a custom field so the Table and Board can group by it.
- Forgetting bulk actions. Select several tasks to assign, move, or delete them together.
- Copying tasks between views. Views never need copies. Switch the view instead.
Connection to Taskade
Tasks are the Memory layer of Workspace DNA: the facts your team works from. Agents read them, and automations create and update them. You can ask an AI agent to generate subtasks from a high-level task description. For the step-by-step, read Add Task / Subtask and Manage Tasks in Learn Taskade.
What You Would Build in Taskade
A support lead asks Taskade Genesis for a ticket tracker. Each ticket is a task with an assignee, a due date, and a Status field, and an automation assigns new tickets. Describe yours and build it free →
Related Concepts
Frequently Asked Questions About Tasks
What is a task in Taskade?
A task is one line in a project. It can hold subtasks, assignees, due dates, tags, custom fields, comments, and files.
How do I add a subtask?
Click a task, press Enter for a new line, then press Tab to indent it. Press Shift + Tab to outdent it.
Can I nest subtasks more than one level?
Yes. Subtasks can nest several levels deep to model a larger breakdown.
Do tasks look different in each view?
The layout differs, but the tasks are the same. An edit in one view appears in all the others.
Can I edit many tasks at once?
Yes. Select several tasks to assign, move, or delete them together.
Can an AI agent create tasks for me?
Yes. You can ask an agent to generate subtasks from a high-level task description.
How do I learn task management step by step?
Read Add Task / Subtask, then Manage Tasks.