Reporting bugs in Flyspray

Bug reports are an essential part of development, and we need you to let us know about programming defects in Flyspray. However, there are a few things that you need to keep in mind when you are thinking about submitting a bug report or requesting a new feature. Please take a few moments to read this brief list of guidelines before you open a new task.

• Take some minutes of your time and read this document, it will teach you how to report a bug correctly.
• We cannot support modified versions of Flyspray. We only accept bug reports on the version that you can get on the download page or from our Subversion repository.
• Always perform a search on both open and closed tasks before opening a new one. Your bug might already have been reported, or your feature requested.
• Use the English language in any tasks you open. Nothing will get done if we can't understand you.
• Only report one bug or request one feature per task.
• If you report a bug, and we mark it as 'requires testing', then please test it and add a comment to the task telling us how well it works.
• If a task is closed and marked 'fixed in devel', then try the development version before requesting that it be re-opened.
• If we deny your request to re-open a task, check the History tab for our reason. If you are unsatisfied with the reason, you are welcome to discuss it on the mailing list.
• Don't demand that things be done. It just annoys us and we will ignore you.
• Be polite. Remember that you got Flyspray for free.
• If you really must have something done immediately, we happily accept donations via Paypal. (See the link on our contributing page).
• Our Flyspray uses the latest development code, so what you you are using on our BTS may not be in the officially released version yet.

If you are happy with the above guidelines, then you are ready to open a new Flyspray task. To raise interest in a task you opened, discuss it on the mailing list.