Updated
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.
Illustrative workflow
Step 1
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.
Step 2
Move it through a status pipeline
Open → In Progress → Fixed → Retest → Verified. Everyone can see exactly where a bug stands.
Step 3
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.
How It Works
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.
Move it through a status pipeline
Open → In Progress → Fixed → Retest → Verified. Everyone can see exactly where a bug stands.
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
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.
Apply this to your workflow
How to Write a Task Description: Template and Examples
A useful task description states the result, why it matters, who owns it and how completion will be checked. Add the inputs, constraints and relevant links so the next person can act without reconstructing the request from chat.
ExploreAcceptance Criteria Examples: A Practical Writing Guide
Acceptance criteria are observable conditions a particular work item must satisfy before it is accepted. Write them around behavior and evidence, including important failure cases. A definition of done sets broader quality expectations across work items.
ExploreBug Report Template: Reproduction Steps, Severity and Evidence
A useful bug report explains what happened, what should have happened, and how to reproduce the difference. Include the environment, impact and safe supporting evidence so the reviewer can investigate without guessing.
ExploreSee Issue Tracking in Your Own Workspace
Free plan available — no credit card required.