The Koha developers make use of a Bugzilla based bug tracking system.
Bugzilla includes a general purpose bug writing guidelines page that you should review in its entirity before submitting a bug to Koha.
All Enhancements or sponsored items will be entered into http://bugs.koha.org which will allow users and developers access to what is currently in development as well as items that are being considered by libraries. Comments can be made on enhancements which will provide details for the development of the enhancement and to work out details with the libraries interested in the enhancement. This page of Enhancement instructions outlines what needs to be put into the enhancement when entering into bugzilla.
A bug can be quickly identified as a problem with Koha. However, it is much more complicated than that. It can be a behavioural problem, or a component that does not work at all. It even applies to documentation that is incorrect. We also utilize Bugzilla for “future enhancements” or “feature requests”.
What is Bugzilla? :Bugzilla is a database of bugs and feature requests developed by the [http://www.mozilla.org Mozilla] project. It helps developers keep track of what's broken and who's fixing it. Users can help by making bug reports clear and specific. The better your bug report, the easier it is to identify the cause, and fix the bug.
:It is very important for Koha to have bugs listed on bugzilla. That is the list that the developers work from. If a bug is just mentioned in a posting to a mailling list, or just mentioned on IRC (chat) it can very easily slip through the cracks.
The first step to submitting a bug is to see if someone else has a similar problem to you.
Congratulations, you found a new bug! Click the new bug button to begin entering a new bug.
| Priority | Description |
|---|---|
| P1 | This bug blocks development or testing work and should be fixed ASAP |
| P2 | This bug blocks usability of a large portion of Koha, and really should be fixed before the next planned release |
| P3 | Seriously broken, but not high impact. Should be fixed before next major release. Can include cosmetic bugs of particularly high visibility, and more minor bugs that are frequently reported |
| P4 | Either a fairly straightforward workaround exists or the functionality is not very important and/or not frequently used |
| P5 | Not that important, just fix when time permits |
| Severity | Description |
|---|---|
| Blocker | Needs to be fixed and an update released immediately. |
| Critical | Koha or component crashes and/or there is a potential loss of data |
| Major | A major part of the component is nonfunctional. |
| Normal | A minor part of the component is nonfunctional. |
| Minor | The component mostly works, but causes some irritation to users. |
| Trivial | The component works with 100% functionality, but has visible typos or other cosmetic problems |
| Enhancement | Generally a feature request for functionality that does not currently exist. These can be useful as guides for future product improvements. |
* 8 Summary: Describe your bug in a short sentence. Be as descriptive as possible- 'it is broken' is not very useful, while 'the text entry form won't let me enter text' is much more informative.
If you think that you may have discovered a bug but are not quite sure or comfortable posting it on Bugzilla post a message to one of the mailing lists and others can give advice: