![]() ![]() Bug is so bad that a release cannot go forth without fixing it Example: bug results in data loss. Needs to be fixed and an update released immediately. If a bug occurs with great frequency, it can be moved up in severity even if it doesn't meet the other criteria in that category. This field describes the impact of a bug on a user. The severity field is quite important as this is what is used to triage the bug reports. The Koha project doesn't currently actively use the 'Priority' field in Bugzilla. If you are unable to find your exact operating system, please pick the closest approximation and in the body of the ticket explain what operating system you are using. In most cases you can leave this as 'PC', as the OS is much more relevant. Verfified this also happens in 16.05, 16.11 and on current master If you have verified the problem in multiple versions, you can pick the newest version to report it against as bug fixes will be backported from the newest to the older versions. You can also note other versions you have tested with in the bug report itself. (If you are unsure of the version of Koha you are using you can find the version in the Staff interface on the "About Koha" page) Select the version of Koha you are experiencing this issue under. If you are unsure what area of Koha to report the error under, view the component list. If you have reproduced the bug in a recent build and no-one else appears to have reported it, then: ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |