Changes between Version 15 and Version 16 of TracTicketsCustomTimeFields

Timestamp:

Apr 13, 2010, 9:30:44 PM (14 years ago)

Author:

hoff.st@…

Comment:

added ideas about clever time value default definitions

TracTicketsCustomTimeFields

@@ -57 +57 @@
   Actually I put it in here, just because I expected opposition against this dependency. I understand your point and made this an own topic under the [#StatusofDevelopment development section] above.
 
+==== Considering demand for custom time field defaults ====
+I can imagine various needs for defaults:
+pre-seed with
+ * empty value (well, thats quite easy :-)
+ * fixed date/time (much less demand, I guess, but this could help i.e. when facing an already fixed project termination)
+ * current date/time
+ * date/time with predefined offset from current date/time (like "now + 14d")
+ * ...
+
+Each one looks like a perfectly reasonable way to preset a suitable default for one of different demands. But only a preset, of course, still subject to change on ticket creation as well during ticket life. It looks like a discussion would help to possibly strip nonsense from sense. We'll see then, how generic or special, simple or complex a default configuration satisfying most/all real world demand would have to become.
+
 ==== Handling ticket changed notification ====
 I plan to let the notification system handle the conversion of unix time stamp values to date/time strings on it's own. I tested with a patched version of [th:wiki:AnnouncerPlugin AnnouncerPlugin] that worked. This is a good start for the [wiki:TracDev/Proposals/Announcer proposed replacement] of current Trac Notification System by Code from [th:wiki:AnnouncerPlugin AnnouncerPlugin]. This might even make per-user preference-based date/time formatting possible in the future.