Skip to content
qarunbookDocs

Raise bugs by email

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.

Before you start

  • An app in live mode. An app being tested asks which check failed, and an email cannot say.
  • To be an admin of the app in qarunbook. Email is on every plan.
  • Any email account to forward from, or customers who can write to an address.

Connect an app, step by step

  1. In qarunbook

    Open the app's Email settings

    Open the app, choose App configuration, then the Integrations tab, and choose the Email tile under Where bugs are reported.

    If the card says email is for live apps, switch the app to live under Settings first.

  2. In qarunbook

    Optional: say who may send

    Under Who may send, put one address or domain per line: example.com lets in everyone at example.com; [email protected] lets in only Ada. Leave it empty to take mail from anyone who has the address.

  3. In qarunbook

    Pick the platforms, then turn it on

    Under Mark emailed issues as affecting, pick the platforms emailed bugs should affect, or none for Every platform. Choose Turn on.

  4. In qarunbook

    Copy the address

    The card now shows This app's address, like bugs+k3x9…@in.qarunbook.com. Choose Copy.

  5. In Your email

    Give it out

    Forward a customer's email to it, put it on your support page, or point a forwarding rule at it.

Check it works

  1. In Your email

    Send a test email with a screenshot

    From your own address, send the app's address an email with the subject Test: email connection, a line of text and a screenshot attached. If you filled in Who may send, send from an address on it.

  2. In qarunbook

    See the issue arrive

    Within seconds the app has a new issue, with the subject as its first line, your message under it. The screenshot appears on it a few seconds after the issue does.

  3. In Your email

    See the reply

    You get an email, Logged as QA-20, saying it is logged with 1 file. It has a Stop these emails link. If you are a teammate on the app, the issue is yours; anyone else is noted as the reporter and emailed again when it is fixed.

How it works

Every message to the address becomes an issue on the app, and the sender is told its code straight away. It is the same issue as one raised in the app, so everything else follows: it is filed in Linear, Jira 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.

  • 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, and so are inline images under 10 KB — signature logos and tracking pixels.
  • Every emailed issue affects the platforms picked on the card, or every platform if none is picked. Change it on the issue when you know more.

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 — in qarunbook, over MCP, through the API, or from Linear or GitHub. Each has a link to stop them.

Anyone who has the address can file a bug — that is what makes it useful. To narrow it, fill in Who may send; mail from anyone else is ignored. If the address ends up somewhere it should not be, choose Regenerate address, then Make a new address: the old one stops working at once. Turn off ignores everything sent to it until you turn it back on; the address stays the same.

Good to know

  • Email brings bugs in and tells reporters about fixes. It never creates checks or sections.
  • If an app goes back to testing, mail to its address is not logged, and the sender is told so.
  • 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.

Something unclear or missing? Write to [email protected].