[teampractices] Scrum-y tools based on BZ (was Re: Scrumbu.gs)

[Steven Walling]

On Thu, Oct 31, 2013 at 9:14 AM, Andre Klapper <aklapper at wikimedia.org>wrote:

> On Tue, 2013-10-29 at 23:12 -0700, Steven Walling wrote:
> > My one worry is that prioritization in Bugzilla is less in our
> > control, and can sometimes be the subject of a tug-of-war with
> > community members.
>
> I haven't seen *larger* editwars on the priority value in Bugzilla so
> far, but as the "Anybody can change the Priority field" concern has been
> brought up by several teams I've talked to, I've created a ticket
> "Consider/Evaluate "Priority" setting restrictions" a while ago:
> https://bugzilla.wikimedia.org/show_bug.cgi?id=54031


Priority is less of a problem than closing a bug. Resolving a bug as
anything except FIXED results in it being reopened regularly. One of the
most important abilities in any prioritization is being able to say "No" to
things.[1] Saying no on Bugzilla often results in "I'm going to act like a
child and reopen a bug you just closed." Our only recourse right now seems
to be to ban someone from BZ, which I am loathe to ask for.

1. http://insideintercom.io/product-strategy-means-saying-no/

-- 
Steven Walling,
Product Manager
https://wikimediafoundation.org/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.wikimedia.org/pipermail/teampractices/attachments/20131031/564642aa/attachment.html>