Re: [Python-Dev] Python tickets summary

Facundo Batista wrote:

2007/11/1, Facundo Batista :

...

...

I think the keyword and keywords interface can be improved. Do you have any plans in that direction? Surely!

But, no, I have no plans to do it, as I can not make cgi scripts in my hosting, so these pages are statics, generated every night, and that's all...

Well, after my hosting allowing CGI, I now improved *a lot* the interface of this page.

Looks much improved! :-)

Now you have more columns:

- Id - Summary - Priority - Severity - Components - Versions - Keywords - Opened by (when) - Temporal location - Last update by (when)

And, the biggest enhancement, you can filter by any combination of:

- Priority - Severity - Component - Version - Keyword

Maybe components and keywords could be combined together and use check boxes so more than one item at a time can be selected? The following suggestions will probably need changes to the data base. Maybe this be done at some point in the future. Ideally the temporal bar could be more like a mini gant/status chart which indicates the status as well as th activity. Maybe the background color can change when the status changes. The possible status sequences might be something like the following. Bugs... 1. bug > bug_confirmed > fix_provided > fix_accepted > fix_applied > closed 2. bug > invalid > closed Features... 3. feature > patch_provided > patch_accepted > patch_applied > closed 4. feature > patch_provided > rejected > closed 5. feature > rejected > closed Filtering on the above status keywords would give good results I think. The fix-provided and patch_provided status items might be split into tests, docs, and patch/fix provided. But that may not be needed. Cheers, Ron

As before, you have everything paged, and with a graph of activity per day at the bottom.

Enjoy it!:

http://www.taniquetil.com.ar/facundo/py_tickets.html

Regards,