A blocker captures a dependency: task A is blocked by task B. You cannot mark A done or continue it until B is resolved (done or cancelled). Rescheduling A is still allowed, since you might be pushing it off until you get to B.
Adding a blocker
In the editor's blocker picker, search by title (tasks in the same project show first). Maptero checks for loops: if adding a blocker would create a circular dependency (A waits on B which waits on A), it warns you (and by voice it refuses the cycle outright). You can also add or remove blockers by voice; if a name is ambiguous, Maptero asks you to pick the one you meant.
How a blocked task looks
- The card turns gray.
- A lock icon appears in the card header.
- A chip shows the blocker's title.
- Hovering the lock lists every blocker.
- Once all blockers are resolved, the lock disappears and a green check chip appears, meaning the task is ready to act on.
What you cannot do while blocked
A task with at least one active blocker cannot be marked done or continued. It can still be rescheduled. If you try to complete a blocked task by voice, Maptero confirms but then tells you the task still has unresolved blockers to complete first.
Cancelling counts as resolving
Cancelling a blocker frees the task it was blocking just as completing it would. A task becomes unblocked when all its blockers are done or cancelled.
Unblock notice
When you resolve a blocker, any task it was holding up shows a green "Task '...' is now unblocked" message so you know it is ready.