Bugtracker

Bugtacker is a software which allow to control and manage reported bugs and future requests, so it is esential for organizing development work and preventing against "reported but forgotten bugs". Reports/problems/future requests are described in so called tickets which are managed like records in database. In fact the bugtracker is the database of tickets for continous development purposes joining, structurlising and prioritising efforts of betatesters, developers and common users.

Before you use bugtracer to report your problem you must read How to Report Bugs Effectively Read it please just to report bugs effectively. You will save lots of nerves and time, yours and ours. Very recommended to make life and development easier and more happy. On linked site translation to many languages are available: English | Português | 简体中文 | Česky | Dansk | Deutsch | Español | Français | Magyar | Italiano | Nederlands | Polski | Русский | 繁體中文 .

Before you will create for the first time your own ticket with problem description, first read how other tickest has been writtten. It will help you to find out used convention, which implies from practise.

Before you will create a new ticket check in existing tickets if anybody else has reported the same problem already. In such case you ought to add your confirmation, description, additional info to this ticket as next comment, so developer will have more info about problem gathered in one place. Many tickets about the same case are not helping, but disturbing as probability of accidental ommiting of important information is incereasing.

In general the report in bugtracker ticket should be as informative, precise, short, easy to understand as possible. Otherwise is just useless.

Efforts to perfect Shareaza can be only as succesfull as good are bug reports. Please have this in mind, because we are open source and your mistakes in reports can kill your efforts and potentialy usefull ideas - give them a chance by writting good reports please.

Currently as bugtracker is used Trac, which is well integrated with SourceForge resources and depository so prefered by coding developers, but not friendly enough for common user due to ancient like interface. Anyway this is current official so take a deep breath and please report bugs there.

At recently lost for project domain as bugtrucker was used Flyspray (currently not officially used) feature request tracker with asorted feature requests. After Will Ervin has devastated that lost domain also content of that bugtacker was lost and in 2009 the Track has become official bugtracker.