#7227 NORM Never A: trac improvement: generate priority report from trac

[Zarro Boogs per Child]

#7227: trac improvement: generate priority report from trac
------------------------------------+---------------------------------------
 Reporter:  ggoebel                 |       Owner:  coderanger      
     Type:  enhancement             |      Status:  new             
 Priority:  normal                  |   Milestone:  Never Assigned  
Component:  trac                    |     Version:                  
 Keywords:  trac report priorities  |    Verified:  0               
 Blocking:                          |   Blockedby:  7221, 7222, 7226
------------------------------------+---------------------------------------
 Per Michael Stone, a list of OLPC priorities can be found
 [http://wiki.laptop.org/go/Priorities-2008 here].

 It would be nice if something similar or a little more detailed could be
 generated from Trac. After all, all priorities should be broken down into
 trac tickets right? What follows is a suggestion on how that could be
 accomplished.

 If #7222, #7221, and #7226 were implemented, it should be to create a Trac
 report which will enumerate trac ticket summaries ordered by some
 combination of Milestone (Release/Branch), Schedule (Month) and Priority
 Grouping (Group By ticket 'Component'?).

 If Trac is modified to facilitate time required estimates, the report
 could also show an indication of hours allocated for a given month,
 allocated hours implemented, allocated hours remaining, and FTE hours
 remaining for the month.

 If a ratio of defect hours per implementation hour can be gathered from a
 running aggregate from historical data. You could also include a rough
 estimate of how many defects tickets you can expect to be entered as a
 result of work that has yet to be started per month.

-- 
Ticket URL: <http://dev.laptop.org/ticket/7227>
One Laptop Per Child <http://laptop.org/>
OLPC bug tracking system