Changes between Version 13 and Version 14 of IcalViewPlugin


Ignore:
Timestamp:
Nov 9, 2015, 9:48:10 AM (8 years ago)
Author:
figaro
Comment:

Cosmetic changes

Legend:

Unmodified
Added
Removed
Modified
  • IcalViewPlugin

    v13 v14  
    55== Description
    66
    7 This plugin provides iCalendar feeds for ticket queries as standard [http://trac.edgewall.org/roadmap roadmap module]. It uses 2 optional custom fields for event date and duration.
     7This 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.
    88
    99== Bugs/Feature Requests
    1010
    1111Existing bugs and feature requests for IcalViewPlugin are
    12 [query:status!=closed&component=IcalViewPlugin&order=priority here].
     12[report:9?COMPONENT=IcalViewPlugin here].
    1313
    1414If you have any issues, create a
    15 [/newticket?component=IcalViewPlugin&owner=xpech new ticket].
     15[/newticket?component=IcalViewPlugin new ticket].
    1616
    1717[[TicketQuery(component=IcalViewPlugin&group=type,format=progress)]]
    1818
    19 == Download and Source
     19== Download
    2020
    21 Download the [download:icalviewplugin zipped source], check out IcalViewPlugin [/svn/icalviewplugin using Subversion], or [source:icalviewplugin browse the source] with Trac.
     21Download the zipped source from [export:icalviewplugin here].
     22
     23== Source
     24
     25Check out IcalViewPlugin [/svn/icalviewplugin using Subversion], or [source:icalviewplugin browse the source] with Trac.
    2226
    2327== Usage
    2428
    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.
     29There 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.
    2630
    2731=== Setup custom fields for date and duration
     
    8488=== Priority
    8589
    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 :
     90iCalendar 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:
    8791
    8892{{{
    89                     'blocker' : 1
    90                     'critical' : 2
    91                     'major' : 6
    92                     'minor' : 8
    93                     'trivial' : 9
     93'blocker': 1
     94'critical': 2
     95'major': 6
     96'minor': 8
     97'trivial': 9
    9498}}}
    9599
     
    107111== Example
    108112
    109 Add a iCalendar links in ticket's queries footer.
     113Add a iCalendar link in ticket's queries footer.
    110114
    111115== Release notes