What a good bug report looks like

(#3879) Announcement
Thanks for helping us fix Fluxer. A clear report is much easier for reviewers to confirm and for us to fix. Here is what we look for.

Before you post

One problem per post

If you found three bugs, please write three reports. The same goes for feature requests: one idea per post, so each can be tracked on its own.

Search first

If someone has already reported it, upvote that post and add what you know in a comment. That helps more than a second report.

Writing the report

A specific title

"Voice drops when switching Wi-Fi networks" tells us far more than "Voice bug".

Reproduction steps

Numbered steps that someone else can follow from a fresh start. For example:
  1. Join a voice call on Wi-Fi
  2. Switch to another Wi-Fi network
  3. Listen for a few seconds
If it only happens sometimes, say how often.

Expected behaviour

What should have happened. One plain sentence is often enough.

Actual behaviour

What happened instead. Include any error message word for word.

Build information

Paste the build string copied from the app, unchanged. The ? next to the Build information box shows where to find it on each platform. "Latest" or "current version" does not tell us which build you are on.

Platform

Tick every platform where you have seen it.

Evidence

Screenshots, a short recording or log lines help a lot. Put files in Attachments and remove anything private first.

What does not belong here

  • Ideas and wishes. Post those as a feature request instead.
  • Questions about how to use Fluxer.
  • Problems caused by another service, such as a network that blocks Fluxer.
  • Security issues. Please follow the security policy and do not post them here.

If your report is sent back

If a report is missing the steps or the build string, a reviewer may send it back with a short reason. That is not a no. Edit the post, add what is missing and it goes back for review.

Comments