Fwd: REST APIs, and Tags

Guy Pyrzak guy.pyrzak at gmail.com
Wed Feb 17 18:03:48 UTC 2010


This is actually a workflow we use at work for triaging our bugs and all we
did was add permissions to status changes so that only particular users
could change a state from "unco" to "ready". I'm not sure of the bug number
bug we find this really useful.

Also I've discussed with a few people that Bugzilla needs a better "triaging
ui". I haven't thought through the whole problem quite yet, and there have
been a few pencil sketches which no one has been super happy with. But I'm
not sure if tagging solves the triaging problem

*attempts to duck out of the rest of this discussion*


On Mon, Feb 15, 2010 at 6:55 AM, Benjamin Smedberg <benjamin at smedbergs.us>wrote:

> On 2/15/10 9:43 AM, Gervase Markham wrote:
>> On 11/02/10 19:01, Frédéric Buclin wrote:
>>> IMO, an additional bug status doesn't fix anything. You move the problem
>>> from UNCO/NEW to NEW/READY.
>> Except that you can't file bugs as READY.
>> And there is a distinction between "yes, this is definitely a problem"
>> (->  NEW) and "this bug report is ready to be fixed" (->  READY).
> This gets into b.m.o-specific workflow, but neither of those states
> represents what I'm really interested in as module owner. What I want to
> know is "have I or my peers looked at this bug, assigned it a
> priority/owner, and commented setting expectations"? There are many bugs
> which have good testcases and are "ready to be fixed" which I have not
> prioritized... in fact many of the bugs filed in the XPCOM component *come
> with patches*, and I still would like to triage them.
> --BDS
> _______________________________________________
> dev-apps-bugzilla mailing list
> dev-apps-bugzilla at lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-apps-bugzilla
> -
> To view or change your list settings, click here:
> <http://bugzilla.org/cgi-bin/mj_wwwusr?user=$MSGRCPT>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bugzilla.org/pipermail/developers/attachments/20100217/1bc18f44/attachment.html>

More information about the developers mailing list