{5} Assigned, Active Tickets by Owner (Full Description) (4 matches)

List tickets assigned, group by ticket owner. This report demonstrates the use of full-row display.

pragma

Ticket Summary Component Milestone Type Created
Description
#29 Trac 0.11 Refactoring component1 Version 2.0 enhancement 07/03/07

The system is presently based on Trac 0.10 and Clearsilver. There are a few sub-tasks in this ticket, that are derived from the Trac Migration Guide:

  • Overhaul all templates for Genshi
  • Rewrite main rendering hook to call Genshi instead of Clearsilver.
  • Rewrite timeline hook
  • Rewrite search hook
  • Modify macros for Genshi compatibility
  • Toss out miniajax in favor of jQuery
  • Remove time rendering from model views, and use "datetime" type instead
  • Normalize module names to match trac module name convention (lowercase)
#33 Sorting Columns component1 Version 2.0 enhancement 03/31/08

With large-ish forums, there needs to be support for sorting columns by clicking on the column header. It should make navigating to popular forums/topics easier to do.

Implementation would be as simple as a link URL with an "&orderby=xyz" argument, funneled into the orderby clause (with some argument sanitation of course).

#38 Beta Migration Checklist component1 Version 1.0 task 04/21/08

There are a slew of things that are needed in order to get the next Beta test of Tracforums ready:

  • Database migration scripts for [70] (in use on Tango project site)
  • Automated database installer for V1.0
  • Possible PHPBB migration script for V1.0

There are also some issues and tickets that are blockers for a Beta release:

  • Finish notification templates
  • Implement cascading deletes in some fashion, likely in code
  • #5
  • #31
  • #36
#28 ORM Improvements component1 Version 2.0 enhancement 07/03/07

The ORM should be enhanced to make for easier maintenance and debugging.

Implementation details for refactoring the existing ORM:

  • ORMColumn to SQL generation and event hooks is sloppy as hell. This needs to be refactored to place these bits in the Column classes
  • Column names in the generated SQL need to be translatable to their respective model within a join, such that they can be individually referenced from where={}. Example: {'model.colname'='foobar'} can translate to "where model_colname = %(foobar)s"
  • SQL generation can be further refined by the use of "prepared statements", since SQL generation currently happens at request time.
  • The Formatter class needs to be factored away to a more generic interface, supported by the formatter methods that currently reside in model.py
  • Look into object caching to accelerate ORMRelation and load() behavior (if needed)
Note: See TracReports for help on using and creating reports.