🧪 killBottleneck is in public beta — cloud and self-host.🧪 killBottleneck is in beta.Beta on GitHub →
Skip to content

Bug reports and ideas

When something does not work, or you think of a way to make it better, you do not have to look for who to write to. The form is inside the app and the message goes straight to whoever runs the instance.

Before you send, you see exactly what travels with the message.

Where to find it

Two ways, both open the same form:

  • under the person icon in the top right — Report a bug or idea,
  • from the left rail — the bug icon. It is on the projects overview, in Tasks and in a map.

The rail is the better one: the app notes which page you were on, so it pays to report from the place where the problem found you.

Bug, or idea

You pick at the top. The only difference is how the message is labelled — both land in the same place.

  • Bug — what you did, what you expected and what happened instead.
  • Idea — what would make your work easier.

What gets sent

By default, anonymously: your text, the app version, the page you were on and your browser. Your address and your company name are not sent — bugs get fixed in the program for everyone, not on individual accounts.

All of it is listed in the dialog before you send; nothing is collected quietly.

Attach a screenshot

Some things are hard to put into words — a screenshot says more. Paste an image straight into the text box with Ctrl+V (copy it from your snipping tool), or use the Attach a screenshot button. The image is automatically scaled down before sending, so there is nothing to prepare, and the "What gets sent" box in the dialog lists it. One click removes it again.

Want a reply?

Tick I want a reply and only then is your e-mail address attached. The message then carries it in Reply-To, so it can be answered straight from an inbox. Without the tick, your address goes nowhere.

What you already sent

The dialog keeps a list of your recent reports with dates, so you can see what you have already raised and do not have to write it twice. Only you see the list — other people's reports are never shown to you.

How many reports you can send

Five per hour per person. It is a guard against accidental repeats, not an attempt to slow you down — for real bug reporting it is plenty.

Self-hosting: the feature must be switched on

On your own installation the form is not offered until you set an address for reports to go to. That is deliberate: an instance should not send anything anywhere without the knowledge of whoever runs it.

Turn it on with KB_REPORT_TO; it also needs working SMTP. Without both, the menu item does not appear at all.

Where reports are stored

Sent reports are also kept in the instance itself. That is what gives you the list of what you sent, and it means a message is not lost even if the e-mail fails to go out — it is then marked as not sent.

After 30 days a report deletes itself. Bugs get fixed right away, so there is no reason to keep the records for long — and it keeps your list readable.

fair-code — self-hosting and internal use are free, reselling as a hosted service is not.