From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Tremer To: development@lists.ipfire.org Subject: Bugzilla Updates Date: Fri, 02 Jun 2017 15:51:48 +0100 Message-ID: <1496415108.23621.29.camel@ipfire.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============6605283710919468225==" List-Id: --===============6605283710919468225== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hello fellow developers, I just implemented a few changes into our Bugzilla instance that I have been wanting to do for a long time now. The motivation for this is that most reporters just create a new bug and set = the priority and severity to "highest." Of the course the latest bug report is always the most important one. When there is no reaction after a day, some people even complain and refer to the priority being high. Obviously all of this doesn't even help anyone. However, there are a lot of bugs in Bugzilla. And that is first of all a good thing. Every documented problem is something that we can deal better with. Ev= en if we don't resolve it straight away. But there are also quite important bugs that need quicker attention. For this, the priority and severity settings were initially designed, but as pointed out above they are hard to use. So I came up with a new concept. This is not brilliantly new, but at least new for us here at IPFire: Instead of having options for "Priority" from "lowest", "low", "normal", "hig= h", "highest", we can now pick between these options: * Will affect all users * Will affect most users=20 * Will affect an average number of users * Will only affect a few users * Will affect almost no one I think this is self-explanatory and just makes clear what this field is for: Determining how many people are affected by a certain problem. The severity field had "low" to "important" as well, but now has been changed to: * Documentation * Localization * Aesthetic Issue * Balancing * Minor Usability * Major Usability * Crash So this will help us to determine how bad a certain problem is and if there i= s a way to work around it or not. The combination of both of them really shows us how important a bug is. For example if you have a Crash that affects all users that is quite bad. If you have a Crash that only affects a few users, this has a rather low importance. So far most bugs are a little bit all over the place since I did not always change these fields back to normal levels and now translated them from the original values to the new ones. Hope this all makes sense for you as well. If there are any questions or comments, please email back! Best, -Michael --===============6605283710919468225== Content-Type: application/pgp-signature Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="signature.asc" MIME-Version: 1.0 LS0tLS1CRUdJTiBQR1AgU0lHTkFUVVJFLS0tLS0KVmVyc2lvbjogR251UEcgdjIKCmlRSWNCQUFC Q2dBR0JRSlpNWHVFQUFvSkVJQjU4UDl2a0FrSHUwVVAvaWVIY25xcE92UXFZSWhRM3g3WThzalgK ZnU3bjZIeUVZK0pLMzF6czVvaTNaOVRLTXJrb3RGQ3ZwVjNmVlQ0ZElqSG16NlNud2tFekt4Wko3 bXJoWFIxZwpXZlNHVXFmc3hObHlubGw0ZkdGM0xIckxnb1FiSVYzdTRkSlNVOWdqcEM5M1lBTldC V0s2Z3N6eThGSys0MWZ1CnpqcGxzS2QzYmZBYzVlWkpJdjE2K2lielpjbnFvMlZrWkhncFFlUnk4 U2tybEZnbEtOQUQyMkJEcGdxNjJZK1oKSlRSWVRJYjZtTUVSYlVITUdwL2lxRDkrMVFnOE1CUFdp K3F2RzN2WjFETlZmeVZ0RkVWK0NlSHltUGdaSG83MApRaHpvUFIyY1F1MXY0S1JCSWpDRDJycmtX b1VzbHB6N3U5LzRaejc0L1lvNUhEOE1mK0NuWWlTVFVEQjN2U0Y0CnVhbTB5alVmNXYxS3ZWc2Nr ZUs1Yi9zaDloSnZibDZoY0VYVFJMUDVieUZhc3I0R0I2TUgxQ09ERlpib3d3aE0KVmxVU2pqdmky ekhhUlp1T3kybzQrNm9jSW50MGZjb0ExYXRnK3dGN1ZuaHBiSVQ0TVBFNjFNYXFsSzVPMGpuMAp4 MndXQjQ4SG1INE5qYmFUSFN2NEovRmY1d1VvVjNpb0FEc3lNUm1PODRCOFRLay9GSENpZTkvVnA3 VEhTOUcxCnJHT2FpSW5OMnlIKzlFZWRPeXRsdFAzb21MV2xjd2d3NFRtcFBiTk8rRXBkVHNCK0tV bmJCSURaQlc0WVUxUmkKVWpOYTFvQTQ3VlJEeFpvc3RhUzh1YnowNEUrVi81K21teXlUU0pVZzk0 a2NkSGpuUVdFMVM1ZnZCeTR1RElRbApoaWVtSERsY3g1LzBMcWZxeUtHZQo9STJLegotLS0tLUVO RCBQR1AgU0lHTkFUVVJFLS0tLS0K --===============6605283710919468225==--