On 07.10.2012 20:06, Christian Boos wrote:
So one way to handle this situation could be to put a ticket which takes more than a few minutes to triage in the "assigned" state, keeping the milestone unset. That way, one could do a "first level" triaging by going through the list of new,reopened tickets with no milestone set, and either triage them properly or give up by "assigning" them to oneself. A "second level" triaging could be done by going through the list of tickets with no milestone set and assigned to *someone else* (what's not trivial for them could perhaps be trivial for me?). Finally, a "third level" triaging would be to really go through the time consuming ones, when there's enough time ahead.
So assigning-to-self would mean: * "not sure how to triage" (if milestone not set) * "accepting and working on it" (if milestone set) Possibly a bit confusing? Wasn't there a "triaging" milestone once? -- Peter -- You received this message because you are subscribed to the Google Groups "Trac Development" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en.
