One tracker, three jobs done well
Most tools pick a side: built for devs and support can't use it, or built for everyone and devs hate it. issueboard is organized around what each role actually needs — and the free roles are genuinely free.
For developers
Fast enough that you stop noticing it
Developers tolerate a tracker only when it stays out of the way. issueboard is built for sub-100ms interactions, full keyboard control, and a model that matches how real codebases work.
Keyboard-first board
Press c to create an issue, / to search, j and k to move through the list. Every common action has a keystroke, and every interaction is engineered to feel instant. No loading spinners between you and 'filed'.
Issues at the org level, spanning many repos
Issues are not trapped inside one repository. One issueboard project links to many code repositories, so a single bug that touches your API, your frontend, and your infra repo is still one issue — with branches and PRs from all of them attached.
PR and branch linking
Attach branches and pull requests from any linked repository to an issue. Status flows back automatically, so the board reflects what is actually merged — not what someone remembered to update.
Close on merge
Reference an issue from a PR and merging it closes the issue. You never have to open the tracker to tell it you finished — the merge already said so.
Search and saved views that work
Fast full-text search plus a clickable filter builder — no query syntax to memorize, and the filters you build can be saved and shared with the team.
Plain defaults, no ceremony
Task / Bug / Idea. To do / Doing / Done / Closed. Done is whatever your team means by it — add Dev done or In QA as statuses — while Closed stays the one moment that notifies reporters and archives the issue. Nothing requires configuration before you can work.
For support
File it in seconds, hear back when it ships
A support agent on a customer call does not have time for a tracker designed for sprint planning. issueboard gives support a free seat, a 30-second filing flow that works from a phone, and a closed loop back when the fix lands.
File from a form, email, or chat
Every project gets a shareable intake form, an email address that turns messages into issues, and chat-based filing. No GitHub account, no paid seat, no training — a magic link in your inbox and you are in.
Follow your own reports
Reporters see the status of everything they filed and can comment on it. No more pinging a developer to ask "any update on that bug from Tuesday?"
Get told when it ships
When an issue you reported or follow is done, issueboard notifies you automatically — with a plain-language status note written for forwarding to a customer, not a commit message.
Customer references on issues
Attach a customer name or support-ticket URL to any issue. Developers see who is affected, PMs can sort the backlog by customer impact, and support can pull up every open issue for one customer in one place.
Works from a phone
The whole flow — file, check status, comment — is mobile-usable, because the moment you need it is usually mid-call, not at a desk.
Triage catches duplicates
Your report lands in the project's triage inbox with duplicate hints, so the same bug filed by three agents becomes one issue with three customer references — not three competing tickets.
For product managers
See across teams without building a second tool
PMs usually maintain a shadow copy of the tracker — a spreadsheet for planning, a Notion doc for the roadmap, a slide for the exec review. issueboard's job is to make the tracker itself answer those questions.
Portfolio across teams and projects
One org-level view of every team and project with status rollups and cross-team filters. No more opening three tabs and mentally aggregating.
Zero-config reports
A handful of opinionated charts — burnup, cycle time, throughput, aging work — that work out of the box with no setup. Not a BI tool, on purpose: the answer to "how is the sprint going" should not require building a dashboard first.
Shareable read-only roadmap
Publish a read-only roadmap view derived from real issue data, at the level of detail you choose. Stakeholders get a link instead of a stale slide deck, and it is never out of date because it is the actual plan.
Org-wide custom fields
Define a field once at the org level and it means the same thing in every team and project. Estimates and priorities stop silently diverging between boards.
Cross-team dependencies
Because issues live at the org level, blocks and blocked-by relations work across teams from day one. The dependency that slips your launch is visible before it slips.
Sub-issues across teams
One problem that hits iOS, Android, and Web becomes a parent with three sub-issues — each routed to a different team with its own assignee and status. The parent card shows “2 of 3 done”, so the whole effort stays visible in one place.
Your own issue types
Task, Bug, and Idea out of the box — or define your own (Incident, Chore, Spike) with a distinct icon and color, per org. Bug and Feature finally look different at a glance, instead of every type reading the same.
AI chat-thread → issueComing soon
A messy chat thread becomes a drafted, correctly routed issue — title, repro steps, suggested priority — confirmed by a human in triage. The signal that today evaporates in chat becomes backlog you can prioritize.
Bring the whole team
Editors, viewers, and reporters each get exactly what they need — and only editors cost money.