[bugs.kde.org] [Bug 413344] Importance field is unclear
https://bugs.kde.org/show_bug.cgi?id=413344 David Edmundson changed: What|Removed |Added CC|k...@davidedmundson.co.uk| -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 413344] Importance field is unclear
https://bugs.kde.org/show_bug.cgi?id=413344 --- Comment #11 from Filipus Klutiero --- (In reply to David Edmundson from comment #10) > >I recommend you add a warning to reporters against bugs.kde.org, with a link > >to more information on your prediction > > Being overly dramatic has opposite effect. Well, are you saying you find Nate's intervention dramatic? If not, I fail to see why a warning conveying the same information would have to be. > In any case this field is for triagers rather than end users. > At worst it's some pointless noise on the screen that they can leave alone. I wish it was, but this field is currently the only one which shows (somewhat) each ticket's importance, which is one of the most important issue properties. > >so apologies if I'm missing something obvious, > > Bugzilla supports locales, this wiki doesn't. So it's one changes as opposed > to many. Thanks for mentioning that consideration. But if that's the only problem, and if (as is visibly the case) we preferred to have definitions only in English, nothing prevents disabling translation for that template (or getting rid of outdated translations each update). And in any case, if this issue is upstream, I fail to see why it couldn't be solved there. > [...] -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 413344] Importance field is unclear
https://bugs.kde.org/show_bug.cgi?id=413344 --- Comment #10 from David Edmundson --- >I recommend you add a warning to reporters against bugs.kde.org, with a link >to more information on your prediction Being overly dramatic has opposite effect. In any case this field is for triagers rather than end users. At worst it's some pointless noise on the screen that they can leave alone. >so apologies if I'm missing something obvious, Bugzilla supports locales, this wiki doesn't. So it's one changes as opposed to many. Bugzilla templates update every bugzilla release. Sometimes they're compatible, sometimes not. -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 413344] Importance field is unclear
https://bugs.kde.org/show_bug.cgi?id=413344 Tom Albers changed: What|Removed |Added Assignee|sysad...@kde.org|n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 413344] Importance field is unclear
https://bugs.kde.org/show_bug.cgi?id=413344 --- Comment #9 from Filipus Klutiero --- (In reply to David Edmundson from comment #7) > FWIW, severity is documented at: > > https://community.kde.org/Guidelines_and_HOWTOs/ > Bug_triaging#Set_Bugzilla_fields In case that wasn't clear, this report is not specifically about severity, but thank you David. > At one point we did also have this in our bugzilla instance in the page > you're referring to, but maintaining the templates separately of upstream is > a hassle. I do not know Bugzilla internals, so apologies if I'm missing something obvious, but I fail to see why maintaining templates separately would be more of a hassle than maintaining wiki pages separately. Unless you just mean write access to that wiki are wider than to the templates (which would be unfortunate). -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 413344] Importance field is unclear
https://bugs.kde.org/show_bug.cgi?id=413344 --- Comment #8 from Filipus Klutiero --- (In reply to Nate Graham from comment #6) > (In reply to Filipus Klutiero from comment #4) > > (In reply to Christoph Feck from comment #2) > > > What is unclear about "Engineers prioritize their bugs using this field"? > > > > No one claimed that was unclear. The problem is this doesn't define what the > > field contains (and has no clear relevance). Imagine I tell you about the > > Oumuamua field which my sister's school added. When you ask me what it > > contains, I tell you my sister and her colleagues use it to optimize their > > work. I then ask you what is the difference between records whose Oumuamua > > is A10 and those whose Oumuamua value is C1. How would you answer? > Your excellent command of English leads me to believe you know what the word > "Importance" means. Alright. In that case, imagine the school's student list has a field called "Letter". Since you surely know what the word "letter" means, what is the difference between students with a Letter value of A10 and those whose Letter value is C1? (Here's a hint: the school's teachers evaluate students using this field.) > I want a better bug reporting UI as much as anyone, but KDE's sysadmins are > in the middle of the GitLab transition and there is no bandwidth available > for improving Bugzilla at this point in time. After that, there are > essentially two options: > - Move from Bugzilla to GitLab issues > - Upgrade out Bugzilla instance to a new version, which has a better UI > > Given those options it doesn't seem to make any sense to put resources into > the current rather old Bugzilla instance. There is unfortunately no new version of Bugzilla. Any of the options you mentioned will take a lot of time to implement if it is chosen. In the meantime, rather than discouraging any request for improvement in the Bugzilla path, I recommend you add a warning to reporters against bugs.kde.org, with a link to more information on your prediction. In any case, if you are implying that a future Bugzilla version already has this issue solved, please indicate so explicitly. -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 413344] Importance field is unclear
https://bugs.kde.org/show_bug.cgi?id=413344 David Edmundson changed: What|Removed |Added CC||k...@davidedmundson.co.uk --- Comment #7 from David Edmundson --- FWIW, severity is documented at: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging#Set_Bugzilla_fields At one point we did also have this in our bugzilla instance in the page you're referring to, but maintaining the templates separately of upstream is a hassle. -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 413344] Importance field is unclear
https://bugs.kde.org/show_bug.cgi?id=413344 Nate Graham changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #6 from Nate Graham --- (In reply to Filipus Klutiero from comment #4) > (In reply to Christoph Feck from comment #2) > > What is unclear about "Engineers prioritize their bugs using this field"? > > No one claimed that was unclear. The problem is this doesn't define what the > field contains (and has no clear relevance). Imagine I tell you about the > Oumuamua field which my sister's school added. When you ask me what it > contains, I tell you my sister and her colleagues use it to optimize their > work. I then ask you what is the difference between records whose Oumuamua > is A10 and those whose Oumuamua value is C1. How would you answer? Your excellent command of English leads me to believe you know what the word "Importance" means. I want a better bug reporting UI as much as anyone, but KDE's sysadmins are in the middle of the GitLab transition and there is no bandwidth available for improving Bugzilla at this point in time. After that, there are essentially two options: - Move from Bugzilla to GitLab issues - Upgrade out Bugzilla instance to a new version, which has a better UI Given those options it doesn't seem to make any sense to put resources into the current rather old Bugzilla instance. -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 413344] Importance field is unclear
https://bugs.kde.org/show_bug.cgi?id=413344 Nate Graham changed: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 413344] Importance field is unclear
https://bugs.kde.org/show_bug.cgi?id=413344 --- Comment #5 from Filipus Klutiero --- Nate, why was this issue marked as resolved? -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 413344] Importance field is unclear
https://bugs.kde.org/show_bug.cgi?id=413344 Nate Graham changed: What|Removed |Added Resolution|--- |NOT A BUG CC||n...@kde.org Status|REPORTED|RESOLVED --- Comment #3 from Nate Graham --- Christoph's answer is correct. You don't need to understand 100% of everything you see to be able to use the bug tracker. :) -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 413344] Importance field is unclear
https://bugs.kde.org/show_bug.cgi?id=413344 --- Comment #2 from Christoph Feck --- What is unclear about "Engineers prioritize their bugs using this field"? The importance field is for the developers so that they can order the bugs in the way they see the need to be fixed. There is no need for users to mess with Alias, Importance, Target, Assignee, Keywords, Depends on, Blocks, Latest Commit, Version Fixed In, and Flags fields. Are you going to report a ticket for each field where you don't understand why they are there? Are you asking why users are able to change them? (Answer: we really only wanted to simplify the life of those that want to help triaging bugs.) Are you reporting all these issues because you want us to swap out Bugzilla for the "modern" options? Bugzilla has served us well the last 20 years, and we get plenty of bug reports. There is no need to invite all but the last user. If your intention is rather to improve Bugzilla, I suggest to report issues directly to Bugzilla developers. KDE sysadmins don't have the resources to maintain their own fork of Bugzilla, so issues really need to be tackled upstream. -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 413344] Importance field is unclear
https://bugs.kde.org/show_bug.cgi?id=413344 --- Comment #1 from Filipus Klutiero --- I forgot to say... if the understanding I described is correct, another reason why Importance is so unclear is that... it really makes no sense. Normally, "severity and "importance" are synonymous in issue trackers (except that "Importance" is more general, as "severity" only applies to bugs). Worse, normally, it is "priority" which is a combining field (combining difficulty/cost and importance). So, if this is solved by fixing the interface and both properties are kept together, "Priority" would be a better name than "Importance". -- You are receiving this mail because: You are watching all bug changes.
