← Back to all guides
Manage work · Project management · ~11 min read

Plane

Live

Track projects with issues, cycles and boards - see what's in progress, what's blocked and what shipped.

See Plane in the tool catalogue →

What is Plane?

Plane is where your team's work is tracked. Every task is an issue; issues live in projects; and you view them as lists, kanban boards or timelines. It replaces Jira, Asana or Linear - lighter than Jira, more structured than sticky notes.

The payoff is one honest answer to "where are we?": what's being worked on, by whom, what's blocked and what's done - visible to everyone without a status meeting.

How it works: a workspace holds projects; each project holds issues. Issues move through states (Backlog → Todo → In Progress → Blocked → Done). Optional cycles (time-boxed sprints) and modules (feature groupings) organise larger efforts.

Getting started

  1. Log in at your company's Plane address with your Brundo account.
  2. Open your team's project from the left sidebar and look at the board view first - it's the quickest mental model: columns are states, cards are issues.
  3. Find your work: click My issues to see everything assigned to you across projects.
  4. Create your first issue: press C anywhere, or click + New issue. Title, assignee, priority, due date - done.

One habit changes everything: if it's work, it's an issue. Tasks that live in chat messages and heads don't get tracked, don't get done, and can't be handed over.

Core concepts

Issues

One unit of work with a title, description, assignee, state, priority and due date. Write titles as outcomes: "Publish pricing page", not "pricing".

States

The columns your work moves through. Your team's defaults: Backlog (captured, not planned), Todo (planned), In Progress, Blocked (waiting on something - say what, in a comment), Done.

Cycles

A time-box, usually 1–2 weeks. Pull issues in at the start; at the end, review what shipped. Unfinished issues roll to the next cycle - visibly, so scope creep is honest.

Modules

Group issues belonging to one deliverable ("Website relaunch") regardless of cycle - useful for tracking a big thing's overall progress.

Views & filters

Any filtered slice (e.g. "all urgent issues assigned to me") can be saved as a view and reused.

Everyday tasks, step by step

Plan a two-week cycle

  1. Create the cycle (Cycles → +), name and date it.
  2. Drag issues from the backlog into the cycle - only what the team can realistically finish.
  3. Everyone gets a sensible load; every issue has an assignee. Unassigned work is unowned work.
  4. During the cycle, work moves across the board. At the end: review, then roll leftovers forward consciously.

Report a task properly

  1. Press C → clear title.
  2. In the description: what "done" looks like, links to relevant files or pages.
  3. Set priority and, if real, a due date. Fake deadlines train people to ignore deadlines.
  4. Assign it - or leave it in Backlog for planning if it's not urgent.

Flag that you're blocked

  1. Move the issue to Blocked.
  2. Comment what you're waiting for and @mention the person who can unblock you.
  3. Blocked issues are reviewed first at the next standup or planning.

Tips & good habits

  • Update the board when things change, not before the meeting. A live board replaces status reports; a stale one creates work.
  • Split anything larger than a couple of days into sub-issues - momentum is visible and handover is possible.
  • Comments on the issue beat DMs about the issue: context stays attached to the work.
  • Use priorities honestly - if everything is urgent, nothing is.
  • Keyboard-first is fast: C creates an issue from anywhere.

Troubleshooting & FAQ

Issue or sub-issue? If it can be finished and verified on its own, it's an issue. If it's a step of something bigger, make it a sub-issue of that bigger thing.

Can clients see our board? Not by default. Projects are internal; if you need client visibility, ask Brundo about options rather than screenshotting boards.

We finished a cycle with leftovers - bad? Normal. What matters is noticing the pattern: if 40% rolls over every cycle, you're planning too much. Adjust.

Can we import from Jira/Asana? Plane has importers. Brundo runs the migration with you - ask us before recreating anything by hand.

Useful resources

Curated for the version Brundo hosts (community / self-hosted editions) — cloud-only or enterprise-only material is skipped.