Updated

Ship & Track

Issue Tracking

Every project gets its own issue tracker, separate from the task board — severity, status, and reproduction steps, without standing up a second tool just to track bugs.

Product Preview
Screenshot of issue tracking in the app
/images/features/issue-tracking.jpg

How It Works

01

Log the issue

Title, severity (critical/high/medium/low), environment, steps to reproduce, and expected vs. actual results — the fields a real bug report needs.

02

Move it through a status pipeline

Open → In Progress → Fixed → Retest → Verified. Everyone can see exactly where a bug stands.

03

Link it to the fix

Optionally connect an issue to the task that resolves it, so the fix and the bug report stay in sync.

Why It Matters

Bugs don't get buried in a general task list where severity is invisible
QA and engineering share one source of truth instead of a spreadsheet handoff
Severity and status are structured fields, not free text in a title
No context-switching to a separate bug tracker for small and mid-size teams

Frequently Asked Questions

Is the issue tracker a separate product or plan?

No — it's included in every project on every plan, including Free.

Can an issue exist without a linked task?

Yes — logging an issue doesn't require a task. Link one later, once you decide how it'll be fixed.

Can I filter issues by severity across a whole workspace?

Yes — the Reports view breaks down open issues by severity and status across projects.