Issue tracking for the whole team — not just the devs.
On issueboard, support agents and product managers are first-class users — free, unlimited, no seat cost. You pay only for the editors who build. Fast, minimal, and zero required configuration.
Public beta · Free while we build · Sign in with Google, Microsoft, or GitHub
Today's trackers leave half the team outside
Bugs reported in chat disappear
A customer issue gets mentioned in Slack or Google Chat, three people say "good catch", and it is never seen again. Someone has to notice it, transcribe it, and file it — and usually nobody does. The team finds out when the customer asks a second time.
GitHub makes non-devs pay for seats
Filing a bug into a private GitHub org requires a paid seat and a GitHub account — even for a support agent who will never touch code. Issues are bound to a single repo, custom fields do not travel between projects, and reporting barely exists.
Jira solves it and nobody wants to use it
Jira can model anything, which is exactly the problem: schemes, screens, and workflow configuration that need an admin to maintain, and a dense UI that non-technical teammates bounce off. The tool that includes everyone should not require training.
What issueboard does
Board & issues
A fast, keyboard-first board with plain-language defaults: Task / Bug / Idea, To do / Doing / Done / Closed. Issues live at the org level — not inside a repo or locked to a team — so cross-team work and blocked-by relations just work.
Triage inbox
Every report from a form, email, or chat lands in a per-project triage inbox. Accept, merge, or decline with one keystroke, with duplicate hints so the same bug filed twice gets caught at the door.
Free reporters & viewers
Unlimited free seats for everyone who reports or watches. Reporters file via a shareable form link or email with magic-link auth — no onboarding, no account dance — and automatically hear back when their issue ships.
GitHub linking
One project links to many repositories. Attach branches and PRs from any of them to an issue, and close it automatically on merge. issueboard links to GitHub — it never replaces it.
AI chat-thread → issue
Coming soonPoint issueboard at a messy 30-message chat thread and get a drafted issue: title, description, repro steps, suggested labels and priority. A human confirms it in the triage inbox — nothing files itself silently.
You pay only for editors
Most trackers charge for every person who needs to see or report anything, so teams ration seats and half the company stays locked out. issueboard charges for exactly one thing: editor seats — the people who get assigned work and edit issues. Everyone else joins free, forever, in unlimited numbers.
That is the whole pricing model. No per-feature gates, no "contact sales" tier for the triage inbox.
How pricing worksEditor
Assigned work, edits anything, manages projects. Admins are editors with org management — same seat price.
Viewer
Full read access and comments — PMs, execs, stakeholders.
Reporter
Files via form, email, or chat. Follows their own reports. Magic-link sign-in.
Frequently asked questions
What is issueboard?
issueboard is a fast, minimal issue tracker for tech product teams where support agents and product managers are first-class users alongside developers. Issues live at the organization level, a project can link to many code repositories, and every report lands in a triage inbox instead of disappearing into chat.
Are viewers and reporters really free?
Yes, free and unlimited, on every plan, permanently. A viewer gets full read access and can comment. A reporter files issues through a form link, email, or chat, then follows their own reports. You only ever pay for editor seats — the people who get assigned work and edit issues.
What exactly is an editor seat?
An editor is someone who does the work inside the tracker: they can be assigned issues, edit anything, and manage projects. Developers are the obvious editors; a hands-on PM might be one too. Admins are editors with org management on top and are billed the same. Everyone else — stakeholders, executives, support agents filing bugs — fits the free viewer or reporter roles.
Does issueboard replace GitHub?
No. issueboard never hosts code. It links to GitHub: one issueboard project can be linked to many repositories, issues link to branches and pull requests across any of them, and merging a linked PR can close the issue. You keep GitHub for code and get a tracker the whole team can actually use.
Is issueboard production-ready?
issueboard is in public beta. The core tracker — boards, issues, search, keyboard-first workflow — is what we use to build issueboard itself every day. Some features described on this site are rolling out during the beta, and billing has not started yet, so everything is currently free.
How do I sign in?
With your existing Google, Microsoft, or GitHub account. issueboard never stores passwords — there are none. Reporters do not even need an account: they use magic links sent to their email.
Try issueboard free
Public beta. Unlimited viewers and reporters, no credit card, sign in with Google, Microsoft, or GitHub.