Changes between Version 27 and Version 28 of TracTicketsCustomTimeFields

Timestamp:

Apr 23, 2010, 1:56:16 AM (14 years ago)

Author:

hoff.st@…

Comment:

updated information according to latest development

TracTicketsCustomTimeFields

@@ -6 +6 @@
  * add 'time' to available types, inheriting most of the definition from 'text', a simple (one line) text field[[BR]]
 
-At that point TracQuery already works as intended by providing from..to
-input fields on selection of custom time fields for query.
-Praise to the flexible, modularized software design of Trac developers!
+At that point TracQuery already shows from..to input fields on selection of custom time fields for query as desired.
+Praise to the flexible, modularized software design of Trac developers! Making it actually work and display results in pretty date/time format is a different thing.
 
-But now at least basic knowledge on how ticket data is handled inside Trac is needed.[[BR]]
+But now more than basic knowledge on how ticket data is handled inside Trac is needed.[[BR]]
 (I found not much hints so had to study the code and initially did most things wrong. A multiple dozen not working or buggy local code revisions later, after discussion in #python, etc. I decided on the implementation detailed below. Please discuss, if you know better, I'm still a Python beginner.)
 
@@ -28 +27 @@
    * patched version of [th:wiki:AnnouncerPlugin AnnouncerPlugin] for now
    * still unsure on patching Trac Ticket Notifications itself, since it looks like almost dead code (sorry, but Announcer is years ahead) and Announcer is already officially attempting to replace Trac Ticket Notifications (see below)
+ * extend ''ticket.query'' and ''ticket/templates/query_results.html'' to
+  * convert custom time strings with POSIX microsecond time stamps from ticket_custom db table to datetime.datetime values
+  * format custom time values for display differently than standard time values
 
 === Status of Development ===
@@ -55 +57 @@
 ==== Known Bugs ====
 Problems (with priority) occurring arround ticket changes
- * (A) {{{TypeError: unsupported type for timedelta microseconds component: unicode}}} on CustomQuery
  * (B) [TracNotification Trac Notification] system unpatched, need to test and investigate, if necessary at all 
 fixed:
- * preview custom time stamp changes is throwing an exception on internal formatting: fixed after realising, that we deal with different formats in _render_property_diff()
+ * {{{TypeError: unsupported type for timedelta microseconds component: unicode}}} on TracQuery: simply needed to take care for conversation of variable type 'string' to a number and handle custom time values in trac/ticket/templates/query_results.html separately from standard time fields
+ * preview custom time stamp changes is throwing an exception on internal formatting: resolved after realising, that we deal with different formats in _render_property_diff()
   a. string with POSIX microsecond time stamp from db, directed to ticket changes list
   b. datetime.datetime values from user input for change-in-progress, directed to preview current custom time field changes