Re: Ticket reports page redesign

On Thu, Mar 24, 2011 at 6:44 PM, Luke Plant wrote: > Have a look and anyone feel free to improve. For me, it has certainly > flagged up the areas we are doing well and badly as core developers, and > the areas where we shouldn't feel so bad. This looks great to me, at

Re: Ticket reports page redesign

On 23/03/11 15:32, Jacob Kaplan-Moss wrote: > On Wed, Mar 23, 2011 at 4:39 AM, Luke Plant wrote: >> It appears to me that this reports page is not nearly as useful as it >> could be, and I'm thinking of redesigning it. > > Sounds just fine for me -- I really threw together

Re: Ticket reports page redesign

On 23/03/11 17:58, Daniel Moisset wrote: > Trac has a way to define reports, usually it would be at /report, but > my guess is that the django trac has it disabled. > > Enabling that allows an admin to define reports (even complex SQL > queries), and/or save custom queries as canned reports. You

Re: Ticket reports page redesign

On Wed, Mar 23, 2011 at 12:32 PM, Jacob Kaplan-Moss wrote: > On Wed, Mar 23, 2011 at 4:39 AM, Luke Plant wrote: >> It appears to me that this reports page is not nearly as useful as it >> could be, and I'm thinking of redesigning it. > > Sounds just

Re: Ticket reports page redesign

On Wed, Mar 23, 2011 at 4:39 AM, Luke Plant wrote: > It appears to me that this reports page is not nearly as useful as it > could be, and I'm thinking of redesigning it. Sounds just fine for me -- I really threw together the first version with very little thought. Feel

Ticket reports page redesign

Hi all, Regarding http://code.djangoproject.com/wiki/Reports It appears to me that this reports page is not nearly as useful as it could be, and I'm thinking of redesigning it. To me, it seems it should structured by the *role* of people who might be involved in Django development, perhaps