What actually happens when you report a bug

It opens a prefilled, public GitHub issue in your browser. Nothing is filed until you press submit there, and the exact diagnostics text is shown to you first rather than hidden behind a checkbox.

Last checked against the app on · View as Markdown

Steps

  1. Open Settings, then General, then About, then Report a bug.
  2. Read the diagnostics block before doing anything else. It shows the exact text that would be attached: app version, operating system, webview version, whether a vault is configured, which background jobs are enabled, and up to the last 4000 characters of a crash log if there is one.
  3. Decline the diagnostics if you would rather not attach them. The report still opens without that block.
  4. Continue, and your browser opens a prefilled issue form on the public releases repository, not the private source repository: only the public one accepts issues from outside the team.
  5. Nothing is sent until you press submit on GitHub itself, and filing needs a GitHub account.

How to tell it worked

The GitHub issue form opens with the fields already filled in, and nothing has been sent until you press the button there.

If it does not work

You are worried the report is filed before you see what is in it.
It is not. The exact diagnostics text is shown to you in the app first, specifically because it can contain absolute paths or note titles from a crash log, and you decide whether to keep that block before anything opens.
You expected a private support ticket.
This route is always the public tracker. If you would rather not have a report visible to anyone, email us instead: that route is private and gets a reply from a person.
You want to know if there is a limit on how many reports you can file.
Nothing in the app limits it. Whatever GitHub itself allows for opening issues is the only limit there is.