Flawsnap
Free trial

Project docs that live next to the bugs

The spec a bug breaks, the test plan that found it and the release note that announces the fix, in the same project as the report.

Project docs in Flawsnap are pages you write inside a project: specs, test plans, release notes. They are organised in a page tree, support comments and @mentions with in-app notifications, can be shared publicly by link, and can be linked to board cards. Docs are included on both Starter and Pro.

Four documents worth keeping here

  • The spec. Link it to the cards it covers, so a developer fixing a bug can check what "correct" was meant to be.
  • The test plan or UAT script. Testers follow it page by page and report with the widget as they go. Start from our UAT checklist.
  • Release notes. Write them as cards reach Done, then share the page with a public link.
  • Known issues. A short page for support, so they can tell a customer "we know, it is on the board".

How docs are organised

Each project has its own page tree, so you nest pages under a parent: a "Release 4.2" page with a test plan and release notes beneath it. Because one project is one website or app, docs never mix with another client's or another product's.

Comments and @mentions

Comment on a doc to ask a question in place. Type @ and a teammate's name to mention them, and they get an in-app notification. Mentions are notified inside Flawsnap; there are no email or Slack alerts for them.

Sharing a page outside the team

Turn on a public share link for a page and anyone with the link can read it without an account. That suits release notes for a client, or a test script for outside testers.

Share only what is meant to be public. Anyone with the link can open the page.

Docs on the board

Cards on the board can link to docs. Open a card and its spec is one click away.

Docs and AI agents

On Pro, an assistant connected over MCP can search, read, write and comment on docs. Ask Claude to draft release notes from the cards in Done, or to check a bug against the spec. Agents cannot change share links or delete docs, and every edit is recorded as you, marked "via agent".

Who can see a doc

Docs follow project access. A member limited to certain projects sees only those projects' docs, which is how agencies keep one client's plans away from another. See team access. Deleting a project deletes its docs along with its reports and board.

Questions

Can I write docs that are not tied to a project?
Docs live inside a project. If you want pages shared across several products, you can create a separate project just for team-wide notes.
Will a teammate get an email when I mention them?
Mentions send an in-app notification inside Flawsnap. There are no email or Slack notifications for mentions.
Do people need an account to read a shared doc?
No. Anyone with a public share link can read that page without signing in.

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

Related

Updated