Bug deadlines (or bug 103636)

Christian Robottom Reis kiko at async.com.br
Wed Jul 28 13:42:04 UTC 2004


On Wed, Jul 28, 2004 at 09:29:03AM -0400, Christopher Hicks wrote:
> On Wed, 28 Jul 2004, Gervase Markham wrote:
> >Sounds like a good plan.
> 
> But you didn't answer any of the other questions that are needed for this 
> to be a plan.  It's a bit bewildering when the Bugzilla Leadership says 
> "beware of going down this path too far" and people ask why and there's no 
> why, it just "is".

He's waiting for me to come up with one <wink>. My plan includes the
following work:

    - Implement initial summary reports for timetracking

          http://bugzilla.mozilla.org/show_bug.cgi?id=250410
        
    - Offer target dates

          http://bugzilla.mozilla.org/show_bug.cgi?id=103636       

    - Implement alternate styling based on time-based information (how
      on-schedule/late we are, how much time we've spent/how much is
      left to do). Probably based on something like

          http://bugzilla.mozilla.org/show_bug.cgi?id=252278

    - Figure out good ways to inform/report on this data (perhaps
      extending the time summary reports, perhaps using charting,
      perhaps using something else).

I don't have anything else planned for timetracking/deadlines -- I
figure if you can obtain basic summaries of this information you're set
for most basic tasks, and by exporting them as CSV you're set to
manipulate it anywhere else. Perhaps others have use cases I haven't
forseen yet.

I *do* however have some work at least planned on that implements "task
groups" per product, where you can define tasks and then group a set of
people per task in a product. This will probably take advantage of
Byron's user-select-picker patch, and Joel's recent group visibility
implementation.

Take care,
--
Christian Robottom Reis | http://async.com.br/~kiko/ | [+55 16] 3361 2331



More information about the developers mailing list