Changes between Version 8 and Version 9 of IcalViewPlugin

Timestamp:

Jul 27, 2009, 3:45:40 PM (15 years ago)

Author:

Xavier Pechoultres

Comment:

--

IcalViewPlugin

@@ -7 +7 @@
 == Usage ==
 
+Zero configuration needed to start using the module. Without start date and duration, tickets can use the due date of associated milestone. To plan tickets the date and duration fields must be set in trac.ini
+
 === Setup custom fields for date and duration ===
 
-To transform a ticket to an event, we need at least a date. Trac only provide a creation date or an update date. So we need a planned date by adding a custom field. The default name is 'dtstart' (see [http://tools.ietf.org/html/rfc2445 RFC/2445]).
+To transform a ticket to an event, we need at least a date. Trac only provide a creation date or an update date. So we need a planned date by adding a custom field, and set this new field as the dtstart field for events in (see [http://tools.ietf.org/html/rfc2445 RFC/2445]).
 
 trac.ini
 {{{
 [ticket-custom]
-dtstart = text
-dtstart.label = Planned Date
-}}}
-
-To use another field name, you can set it in a new configuration section named 'icalendar' :
-
-{{{
-[ticket-custom]
-my_custom_dtstart = text
-dtstart.label = Planned Date
+my_custom_dtstart_field = text
+my_custom_dtstart_field.label = Planned Date
 
 [icalendar]
-dtstart = my_custom_dtstart
+dtstart = my_custom_dtstart_field
 }}}
 
@@ -32 +26 @@
 {{{
 [ticket-custom]
-dtstart = text
-dtstart.label = Planned Date
+...
+my_custom_duration_field = text
+my_custom_duration_field.label = Duration in days
 
-duration = text
-duration.label = Duration in days
-}}}
-
-To use another field name :
-
-{{{
 [icalendar]
-duration = my_custom_duration_field_name
+duration = my_custom_duration_field
 }}}