Updated
Bug & Issue Tracking
A bug isn't a task with a red label — it needs its own fields, its own severity, and its own status pipeline. Every project has one built in, so a small team never has to run two tools.
How to Do This in My First Task
Log the bug with real detail
Title, severity (critical/high/medium/low), environment, steps to reproduce, and expected vs. actual results — captured once, correctly.
Move it through a status pipeline built for QA
Open → In Progress → Fixed → Retest → Verified — a status model that matches how bugs actually get resolved, not a generic to-do/done.
Link it to the task that fixes it
Optionally connect the issue to the task where the fix is being built, so the bug report and the work stay linked.
Track severity across the whole workspace
Reports break down open issues by severity and status, so a spike in critical bugs is visible before it's a fire drill.
Features You'll Use
Why It Matters
Frequently Asked Questions
Do I need a separate Jira instance to track bugs?
No — every project's issue tracker is built in and included on every plan, including Free.
Can I report a bug without knowing which task will fix it?
Yes — an issue doesn't require a linked task. Connect one later once you've decided how it'll be resolved.
Can external testers or QA-only teammates log issues?
Yes — invite them with a Member role scoped to the relevant workspace, so they can create and comment on issues.
Try It With Your Own Work
Free for teams up to 10 — no credit card required.