On 13/10/2016 4:56 PM, Adam Williamson wrote: > On Thu, 2016-10-13 at 14:40 +1000, Jeff Fearn wrote: >> On 13/10/16 14:02, Adam Williamson wrote: >>> On Wed, 2016-10-12 at 21:09 -0400, Josh Boyer wrote: >>>> On Wed, Oct 12, 2016 at 8:33 PM, Adam Williamson >>>> <adamwill@xxxxxxxxxxxxxxxxx> wrote: >>>>> On Wed, 2016-10-12 at 09:55 -0400, Josh Boyer wrote: >>>>>> All of the extra app stuff could be avoided if we disallowed reporters >>>>>> (or random people) to change the Severity and Priority fields. >>>>> Mmm, I don't really think so. Presumably it would be maintainers who >>>>> got to set those fields, right? But they are doing so in relation to >>>> No, why would you presume that? >>> I dunno, just seemed logical. That's how they're intended to be used at >>> present. Bug reporters aren't supposed to set them and don't have the >>> privilege purely by rights of having an account >> This is true for priority but not true for severity. Severity is the >> external, i.e. reporters, weighting >> of the bug and you do not need to be in editbugs to set it. > That's not the intent of the fields as I understand them. 'severity' is > supposed to represent how bad the bug is, whereas 'priority' is > supposed to represent how important it is to get it fixed compared to > other bugs in the same component. They're obviously related, but not > the same, and it's not "severity is the reporter's opinion, priority is > the maintainers' opinion", no. My understanding is based on ye olde services plan: "Bugzilla Severity and Priority When filing a new bug report, or actioning an existing bug, it is important to bear in mind that, while both the 'Severity' and 'Priority' fields are required; 'Priority' is an internal weighting and 'Severity' is customer weighting. This distinction can cause confusion if not consistant." This is only significant in that it may have impacted the way they are coded on BRC. > I think you might be right that we allow the bug reporter to set > 'severity', though. BRC carries a custom patch to restrict priority to a group besides editbugs group (the setpriority group), AFAICT there is no code that allows similar restriction of the severity field. Cheers, Jeff.
Attachment:
signature.asc
Description: OpenPGP digital signature
_______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
