Getting started

Adding tasks and organising them into groups

Adding tasks, organising them into groups, creating subitems, reordering by drag, and the task limits on each plan.

Groups come first

Every task belongs to a group. Groups are how a project is divided: by workstream, by delivery team, by phase, or by stage, whichever matches how the work is actually run. Templates arrive with their groups already created, and you can rename, add, and reorder them at any time.

Groups are not just visual. The Board view uses them as columns, the dashboard breaks numbers down by them, and exports carry them through.

Adding tasks

Add tasks directly in the table. A task carries a name, a group, planned start and end dates, a percentage complete, an owner, and an impact rating. Everything else -- dependencies, cost, effort, custom columns -- is optional and can be filled in later.

A task can also be a milestone rather than a normal task. Milestones have no duration and render as diamonds on the timeline, which is what makes them readable as decision points rather than work.

Subitems

A task can sit underneath another task as a subitem, giving you a two-level structure without creating a separate project. Subitems render as a nested board inside the parent row and use the same columns as the main table.

Parent tasks stretch to cover their children automatically. A parent never shows an end date earlier than the latest thing inside it, so a slipping subitem visibly moves its parent without you having to keep the parent dates in step by hand.

Reordering

Drag a row to move it. Dragging within a group changes its position; dragging into another group moves it there. A parent dragged to a new group takes its subitems with it.

Only the rows that actually moved are written, so reordering a large table does not rewrite the whole project.

Task limits per plan

Starter allows 50 tasks per project, Basic 200, Standard 400, and Professional 600.

The limit applies per project, not per account, and it is enforced in the database rather than only in the interface. Nothing is ever deleted when you reach a limit: the action that would exceed it is blocked and you are told which limit you hit.

Related articles

Creating your first project

How to create a project in Depentra, what the three starting points give you, and how many projects your plan allows.

Creating dependencies, with lag and lead time

How to link tasks so one waits on another, how to add lag or lead time, and why circular chains are blocked.

Choosing and applying a template

What a Depentra template installs, which plans can use which templates, and what happens if a template is larger than your task limit.

Still stuck?

If this did not answer your question, tell us what you were trying to do and we will help.