English Catalan
In this documentation we use the term *bug* to refer to a software error.
Remember that **the more effectively you report a bug**, the more likely we are to fix it.
Have a look at:
the [[list of known issues|support/known_issues]]
If that is not possible, try to **describe what went wrong in detail**. Write down the error messages, especially if they have numbers.
Write **clearly and be precise**. Say what you mean, and make sure it cannot be misinterpreted.
Be ready to provide extra information if the developers need it. If they did not need it, they would not be asking for it.
You can also refer to the great [How to Report Bugs Effectively](http://www.chiark.greenend.org.uk/~sgtatham/bugs.html), by Simon Tatham.
WhisperBack will help you fill-up a bug report, including relevant technical details and send it to us encrypted and through Tor.
The first aim of a bug report is to **tell the developers exactly how to reproduce the failure**, so try to reproduce the issue yourself and describe how you did that.
Reporting bugs is a great way of helping us improve Tails.
[[!meta title="Reporting an error"]]
Start WhisperBack
the [[!tails_gitlab groups/tails/-/milestones desc="list of things that will be fixed or improved in the next release"]]
Write the report
WhisperBack lets you give plenty of useful information about your bug:
**Summary** a summary of the bug, try to be short, clear and informative
**Name of the affected software**
**Exact steps to reproduce the error**
**Actual result and description of the error**