Issue tracking
Every issue has an owner, history and next step.
Each bug, feature, task or epic is one issue, with a key you can say out loud, the people on it, a status from your project’s own list and every change kept in its history.
Open the issue and the whole story is there.
ACME-12 is a Major bug in the Acme project, now fixed. Read it in the issue list, on its own page, or as the history of every change made to it.
Invite link blank after it expires
Steps. Open an invitation link that is older than seven days.
Expected. A message that the link has expired and a way to request a new one.
Actual. A blank page.
- Parent for 1
ACME-13Invite expiry date shown in UTC- Depends on 1
ACME-4Invite expiry setting per org- Referenced by
- Invitation links and expiryKnowledge base
- Attachments 1
- invite-expired.log18 KB
- Status
- Fixed
- Assignee
- Alex Lee
- Estimation
- 2h
- Spent time
- 1h 45m of 2h
- Sprint
- Sprint 08
- Due date
- 9 Oct 2026
Fields
- Severity
- Critical
Created by Casey Kim, 2 Oct 2026. Updated by Alex Lee, 8 Oct 2026, 4:40pm.
s status · a assignee · e description
- Casey Kim created the issue2 Oct 2026, 9:05am
- Casey Kim Assignee: Unassigned → Alex Lee, Estimation: 2h, Due date: 9 Oct 20263 Oct 2026, 10:14am
- Casey Kim Sprint: Sprint 08, Story points: 33 Oct 2026, 10:14am
- Alex Lee linked: depends on ACME-45 Oct 2026, 11:28am
- Alex Lee Severity: High → Critical5 Oct 2026, 11:30am
- Alex Lee linked: parent for ACME-135 Oct 2026, 11:34am
- Alex Lee Status: Open → In Progress6 Oct 2026, 9:20am
- Alex Lee logged 20m, Development6 Oct 2026, 9:21am
- Alex Lee attached invite-expired.log6 Oct 2026, 2:12pm
- Alex Lee logged 1h 25m, Development8 Oct 2026, 4:38pm
- Alex Lee Status: In Progress → Fixed8 Oct 2026, 4:40pm
Hand-drawn product views with fictional data. A correction made within five minutes updates the history entry instead of adding a second one.
From bug report to resolved issue, without losing the thread.
Six steps on ACME-12, each one recorded where the next person will look: on the issue, in its history, and in the inbox of whoever needs to know.
Your lists, no transition rules.
Statuses, priorities and types are lists each project edits. Any status can follow any status. Each status belongs to a category, and a done or cancelled one marks the issue resolved.
- Statuses
- Submitted, Open, In Progress, Reopened, Can’t Reproduce, Duplicate, Fixed, Won’t fix, Obsolete, Closed
- Priorities
- Show-stopper, Critical, Major, Normal, Minor
- Types
- Bug, Feature, Task, Epic
What a new project starts with. A Project Admin adds, recolours and deletes values, and picks each list’s default.
Casey files the bug.
Only a title is required. Status, priority and type start at the project’s defaults, so Casey writes the steps to reproduce in Markdown and raises the priority to Major.
Casey Kim created ACME-12 · Bug · Open · Major
Alex takes it.
Assignee, estimate and due date saved together make one history entry. Being assigned makes Alex a watcher, so new comments and status changes reach Alex’s inbox.
Assignee: Unassigned → Alex Lee · Estimation: 2h · Due date: 9 Oct 2026
It gets a subtask and a dependency.
A parent for link puts ACME-13 under it. A depends on link to ACME-4 shows on both issues, in both histories, and can never loop back on itself.
ACME-12 parent for ACME-13 · depends on ACME-4
The log goes on the issue.
Drop the file onto the editor or paste a screenshot. Files are private: a link opens only for someone signed in who can open the issue.
Alex Lee attached invite-expired.log
The reproduction is discussed in place.
A comment mentions @casey, who is told in the inbox. ACME-4 typed in the text becomes a link, struck through once that issue is resolved.
@casey reproduced with a ten-day-old link. The log shows the token check returning before the page renders. The fix waits on ACME-4.
It is resolved, with the record intact.
Fixed is a done status, so the issue is marked resolved and the time recorded. Casey, who filed it, hears that it was resolved.
Status: In Progress → Fixed · resolved 8 Oct 2026, 4:40pm
A Severity field, only on the bugs.
A Project Admin adds it under Project settings → Fields. From then on it sits in each bug’s sidebar, in the issue list, in search and in the CSV export, and an agent reads and sets it by name.
- Name
- Severity, renamed whenever you like
- Slug
- severity, the name search uses; it never changes
- Type
- Select, with Low, High and Critical
- Applies to
- Bug only, so it never clutters an Epic
- Required
- Yes, with High as the default
- Empty label
- No Severity
A required field must have a value when an issue is created and cannot be cleared afterwards; the default counts. Bugs filed before it became required keep their empty value, shown as No Severity. Change an issue to a type the field does not apply to and the field disappears, its value kept for when the type changes back.
Group the list or the Issues per field report by Severity, and sort by it in its option order.
Read about custom fieldsSeverity on ACME-12
On the issue
- Issue
- ACME-12Invite link blank after it expires
- Type
- Bug
- Severity
- Critical
In search
In the CSV export
Key,Title,Type,Priority,Severity
ACME-12,Invite link blank after it expires,Bug,Major,CriticalHand-drawn product views with fictional data. Two other bugs in ACME are Critical.
The same ACME-12, wherever the work goes next.
One key, one record. The board, the reports, the knowledge base and your agent all read the issue you just saw, not a copy of it.
Where did ACME-12 end up, and is anything still open on it?
- get_issueissue: "ACME-12", detail: "full"
ACME-12 Invite link blank after it expires is Fixed, resolved 8 Oct 2026, 4:40pm, assigned to Alex Lee. Severity Critical, 1h 45m spent of 2h.
Nothing is left open: its subtask ACME-13 and ACME-4, which it depends on, are both Fixed. The decision is in the article Invitation links and expiry.
On the sprint board.
Planned into Sprint 08 with 3 story points, ACME-12 is a card with its key, title, priority, people, points and subtask progress. On a board by status, moving the card changes its status.
Sprint 08 · ACME-12 · 3 points · 1/1 subtasks done
Sprints and boardsIn the reports.
Issues per field, grouped by Severity, counts ACME-12 under Critical. Click the bar and the issue list opens with exactly the issues it counted.
Issues per field · Severity · Critical 3
Project reportsBeside the decision.
The knowledge base article on invitation expiry mentions ACME-12, so the issue lists it under Referenced by. Whoever picks the bug up finds the reasoning.
article://ACME/invitation-links-and-expiry → ACME-12
Knowledge baseIn your agent.
Through MCP an agent reads, files and updates issues with the same keys, names and permission checks as the app, and every change is recorded under your name.
get_issue · search_issues · get_issue_activity
MCP and AI agentsFive roles, and a way back from mistakes.
There are no permission schemes to design. Each person has a role in each project, an agent can never do more than the person it acts for, and the same rules hold in the app, the API and MCP.
- Observer
- Reads the project’s issues, comments and files. Stars, watches and votes. Changes nothing.
- Contributor
- Creates and edits issues, comments, links, attaches files, logs time and sets custom field values.
- Project Admin
- Also deletes and restores issues, edits anyone’s comments and shapes the project’s lists and fields.
- Org Admin
- Project Admin on every project in the organisation, plus members and settings.
- Org Owner
- Everything an Org Admin can, plus transferring ownership.
Deleted, then restorable for 14 days.
A Project Admin confirms the delete and the issue leaves the project at once. For 14 days it comes back from the Undo that follows or from the project’s list of deleted issues, with its comments, time, files and history.
ACME-12 deleted · Undo
People who leave keep their name.
Everything a former colleague did keeps their real name and picture, with a Former member label, never “Deleted user”. Their work stays searchable.
created by: @alex
Issues leave as CSV whenever you like.
Export any list exactly as searched and sorted, up to 10,000 issues, with the columns you choose, custom fields included. Issues come in from any CSV, with a column mapping and a dry run first. There is no native importer from another tracker.
Questions about issues.
What teams ask before they move their bugs across. Short answers here, the rest in the manual.
Do we have to set up a workflow before filing the first bug?
No. A new project starts with statuses, priorities and types you can use straight away, and a Project Admin edits them as lists. There are no transition rules: any status can follow any status. Moving an issue into a done or cancelled status marks it resolved. Statuses and resolution
How do custom fields fit into search and export?
Each field has a slug that search uses, such as severity: Critical. You can sort and group the issue list by it, add it as a column, count it in a report and include it in the CSV export. A project can have up to 50 active fields, in 13 types from text and dates to people and durations. Custom fields
What happens if someone deletes an issue by mistake?
Only Project Admins can delete an issue, and they are asked to confirm. For 14 days it can be restored from the Undo that follows or from the project’s list of deleted issues. After that it is removed for good with its comments, time entries, attachments and history.
Can we bring our existing issues across?
Issues export to CSV today, with the columns you choose. Issues come in from any CSV through a column mapping and a dry run. There is no native importer from another tracker; an agent connected to both trackers can help carry issues across, with you reviewing how people and fields map. Moving with an agent
Who can open the files attached to an issue?
Only people signed in who can open the issue. A file link pasted into a chat does not open for anyone else, and stops working for someone who loses access. A file can be up to 100 MB, and an issue can hold 50.
What happens to issues when someone leaves?
Everything they did keeps their real name and picture, with a small Former member label. You can still search for their work, but they are no longer offered when you assign or mention someone.
File your first bug in a few minutes.
Join the beta, create a project, and its statuses, priorities and types are ready. Add a Severity field when you need one.
ACME-4.