If I resolve a report, does the card move?

Yes. Once a report is tracked, its status is picked from the board’s lists, and choosing one moves the card. The report’s status then follows the card’s stage.

Does each project have its own board?

Yes. One project is one website or app, with its own reports, board and docs.

Can clients see the board?

Only people you invite to your organization can sign in. You can limit a member to specific projects, so a client sees their own project's board and nothing else.

A Kanban board where bug reports become work

Reports arrive with the proof; the board is where your team decides what happens to them next.

The Flawsnap board is a Kanban board inside each project. Bug reports become cards that move through lists such as Backlog, Todo, Bugs, In Progress, QA and Done, and the report's status follows its card automatically. Cards carry priority, assignee, labels, due date, linked docs and comments. It is on both plans.

The lists you start with

A new board has six lists: Backlog, Todo, Bugs, In Progress, QA and Done. Each list has a stage role (backlog, todo, bugs, in progress, QA, done, or custom for lists you add), and that role is what keeps report status in step with the board.

Card is in a list with stage	The linked report shows
In progress or QA	In progress
Done	Resolved

Rename or add lists to suit your process. Give each a stage role so the sync knows what it means.

Two ways a report gets onto the board

By hand: open a report and choose Track on board. It becomes a card in the Bugs list. Use this when someone triages first and only real bugs go on the board.
Automatically: turn on auto-add in the project settings, and every new report is put into Backlog as a card with its priority. Use this when the board is your inbox.

What a card holds

A title and a rich description
Priority and an assignee
Labels. The defaults are Design, Backend, Frontend, QA and Rollback
A due date
The linked report, with its screenshot and logs one click away
Linked project docs, such as the spec the bug breaks
An activity log with comments

Sending a fix back from QA

When a tester finds the fix did not hold, QA chooses Send back on the card and gives a reason. The card returns to In Progress, the Rollback label is added automatically, and the card shows how many times it has been sent back. The activity log stays on the card, so whoever picks it up again sees what was tried.

Board, List and Grid views

Drag and drop cards on the Board view, scan many at once in List, or browse visually in Grid. Filter by text or card number, by label and by assignee, for example "everything assigned to me with the Frontend label".

Agents can move cards too

On Pro, a coding agent connected over MCP can pick up a card with start_task (it moves to In progress), read the report, make the fix and call finish_task, which moves the card to QA or Done with a summary and a link to the pull request. Every move is recorded as the person who connected the agent, marked "via agent".

What the board is not

It is a focused board for bugs and the work around them. There are no sprints, epics or time tracking, and no sync with Jira, Linear or GitHub Issues. If you run those, see bug tracking vs issue tracking for how teams split the two.

Questions

If I resolve a report, does the card move?: Yes. Once a report is tracked, its status is picked from the board’s lists, and choosing one moves the card. The report’s status then follows the card’s stage.
Does each project have its own board?: Yes. One project is one website or app, with its own reports, board and docs.
Can clients see the board?: Only people you invite to your organization can sign in. You can limit a member to specific projects, so a client sees their own project's board and nothing else.

Try it on your own site

7-day free trial, then $9 a month for Starter or $19 for Pro, per organization, with unlimited team members.

Start free trial Try the live demo

Updated 10 November 2026