Raise bugs by email — qarunbook API docs

Most bug reports already arrive as email. Give the app an address, forward them there, and each one is an issue on the app — no copying across, and nothing to install.

The shape of it

Each live app can have a private address, like bugs+k3x9…@in.qarunbook.com.
Forward a customer's email to it, put it on your support page, or point a forwarding rule at it.
Every message becomes an issue on the app, and the sender gets a reply straight away: Logged as QA-41.
When the issue is marked fixed — in qarunbook, over MCP, through the API, or from Linear or GitHub — the person who reported it is told.

It is the same issue as one raised in the app, so everything else follows: it is filed in Linear or GitHub if the app is connected, it can be given a priority and people to fix it, and it counts towards Free's monthly allowance of issues.

Turn it on

Open the app, choose Configure, then the Integrations tab, and find Email. You need to be an admin of the app.
Choose Turn on. The address appears; Copy it and give it out.

Email is for apps in live mode, where a bug does not need a check. An app being tested before release asks which check failed, and an email cannot say — so switch the app to live under Settings first. If an app goes back to testing, mail to its address is not logged, and the sender is told so.

What becomes the issue

The subject is the first line, and the message follows it. Re: and Fwd: are taken off the subject.
Quoted replies and signatures are left out — the issue is what the sender wrote, not the thread under it.
A forwarded email keeps the forwarded message, with who sent it and when, because that is the report. Your own note above it is kept too.
Images, screen recordings and PDFs are attached to the issue, the same as files added in the app. Other files are left out.
Every emailed issue affects the platforms you pick on the card, or every platform if you pick none. Change it on the issue when you know more.

Who it says reported it

When the sender has an account with access to the app, the issue is theirs, exactly as if they had raised it in the app — and they hear that it is fixed the way they always do, not twice. Anyone else is noted as the reporter: the issue reads Ada Lovelace via email, her address is stored with the issue, and the REST API returns her as reporter.

An outside reporter gets two emails, and no more: Logged as QA-41 when it arrives, and Fixed when it is marked fixed. Each has a link to stop them.

Keeping the address yours

Anyone who has the address can file a bug — that is what makes it useful. If that is wider than you want:

Who may send takes addresses and domains, one per line. example.com lets in everyone at example.com; ada@example.com lets in only Ada. Mail from anyone else is ignored.
Regenerate address makes a new one and stops the old one at once — for when it has ended up somewhere it should not be.
Turn off ignores everything sent to it until you turn it back on. The address stays the same.

Good to know

Automatic mail is ignored: out-of-office replies, bounces, mailing lists, and anything marked Auto-Submitted or Precedence: bulk. Nobody gets a reply to a robot.
An address takes up to 60 emails an hour, and 10 an hour from any one sender. Beyond that, mail is ignored until the hour is up.
Messages up to 25 MB are accepted, and up to 10 files from each. Files still count towards the workspace's storage, and one that would take it past the plan is left off — the reply says which.
Mail sent to an address that does not exist, or one that has been replaced, is dropped without a bounce.
A message delivered twice is logged once.
On Free, once the month's issues are used up, emailed reports are not logged until the allowance comes back.
Senders with a no-reply address are logged but not replied to.