Will try to make comments inline... had to change email client.
On 25/2/20, 10:31 am, "Edward Welbourne" <edward.welbou...@qt.io> wrote:
Mitch Curtis (25 February 2020 10:23) elaborated on what he'd said earlier:
>> For some context and for those who don't know: within the company, we
>> now have weekly bug triaging where a team of two people prioritise
>> all unprioritised bugs. So new reports rarely go more than a few days
>> without having a priority set. We've been doing this for a few years
>> (?) now and it works quite well.
> Someone just reminded me that some devs within the company don't have
> approver rights yet, which is a good point.
(Full disclosure: I was that someone.)
> So I'll revise my question:
> Why do we allow users who are unfamiliar with our conventions about
> priority values to set the priority of a bug report?
How about: because we can always over-ride them if we really disagree;
and their prioritising of the bug is an opening for discussion of why
it's so important to them - which, after all, we might have missed.
I'd rather have a dialog than a privilege,
We do have a means for dialog: the comments, which reporters kinda have to use
to communicate their thoughts about the priority of the report, regardless of
whether or not they can change the priority. So at that point it's more of a
gesture of good will, which I understand, but just seems like extra work for
everyone when the priority is inevitably restored to the previous value.
I would say a far greater privilege is being able to close a report, and that
too will result in dialog via the comments section if the reporter is unhappy
with the resolution.
Eddy.
_______________________________________________
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
