Changes between Version 13 and Version 14 of IcalViewPlugin
- Timestamp:
- Nov 9, 2015, 9:48:10 AM (8 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
IcalViewPlugin
v13 v14 5 5 == Description 6 6 7 This plugin provides iCalendar feeds for ticket queries as standard [http://trac.edgewall.org/roadmap roadmap module]. It uses 2 optional custom fields forevent date and duration.7 This plugin provides iCalendar feeds for ticket queries as standard [http://trac.edgewall.org/roadmap roadmap module]. It uses 2 optional custom fields: event date and duration. 8 8 9 9 == Bugs/Feature Requests 10 10 11 11 Existing bugs and feature requests for IcalViewPlugin are 12 [ query:status!=closed&component=IcalViewPlugin&order=priorityhere].12 [report:9?COMPONENT=IcalViewPlugin here]. 13 13 14 14 If you have any issues, create a 15 [/newticket?component=IcalViewPlugin &owner=xpechnew ticket].15 [/newticket?component=IcalViewPlugin new ticket]. 16 16 17 17 [[TicketQuery(component=IcalViewPlugin&group=type,format=progress)]] 18 18 19 == Download and Source19 == Download 20 20 21 Download the [download:icalviewplugin zipped source], check out IcalViewPlugin [/svn/icalviewplugin using Subversion], or [source:icalviewplugin browse the source] with Trac. 21 Download the zipped source from [export:icalviewplugin here]. 22 23 == Source 24 25 Check out IcalViewPlugin [/svn/icalviewplugin using Subversion], or [source:icalviewplugin browse the source] with Trac. 22 26 23 27 == Usage 24 28 25 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 your `trac.ini` file.29 There is no 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 your `trac.ini` file. 26 30 27 31 === Setup custom fields for date and duration … … 84 88 === Priority 85 89 86 iCalendar supports the priority tags, but uses an integer from 1 (highest) to 9 (lowest). So we need a map to transform Trac priorities to integer. The plugin integrate a default mapping:90 iCalendar supports the priority tags, but uses an integer from 1 (highest) to 9 (lowest). So we need a map to transform Trac priorities to integer. The plugin integrates a default mapping: 87 91 88 92 {{{ 89 'blocker' :190 'critical' :291 'major': 692 'minor': 893 'trivial': 993 'blocker': 1 94 'critical': 2 95 'major': 6 96 'minor': 8 97 'trivial': 9 94 98 }}} 95 99 … … 107 111 == Example 108 112 109 Add a iCalendar link sin ticket's queries footer.113 Add a iCalendar link in ticket's queries footer. 110 114 111 115 == Release notes