| 81 | == Extended configuration == |
| 82 | The development version of this plugin addes support for keyword arguments. This could make macro invocations more readable and maybe even shorter than before, as long as you largely stick to the defaults and just want to change one or two values. Supported keywords are (with default values here): |
| 83 | {{{ |
| 84 | nav = true - navigation link switch, same as 'showbuttens' |
| 85 | wikipage="%Y-%m-%d" - same as 'wiki_page_format' |
| 86 | template="" - same as 'wiki_page_template' |
| 87 | query="id!=0" |
| 88 | }}} |
| 89 | The ''query'' keyword actually supports any expression supported by TracQuery. This is the single new ticket selection logic and can use custom field values as well as expressions chained by AND (OR since 0.12). An invalid expression was chosen on purpose to select and show all tickets by default. |
| 90 | |
| 91 | The plugin optionally makes use of an own configuration section, that could be placed into 'trac.ini' as follows: |
| 92 | {{{ |
| 93 | [wikiticketcalendar] |
| 94 | ticket.due_field.name = due_close |
| 95 | ticket.due_field.format = %y-%m-%d |
| 96 | ticket.due_field.utcoffset = 0 |
| 97 | }}} |
| 98 | |
| 99 | Again these are the implicit default values. A useful alternative configuration would look like |
| 100 | {{{ |
| 101 | [wikiticketcalendar] |
| 102 | ticket.due_field.name = due_date |
| 103 | ticket.due_field.format = ts |
| 104 | ticket.due_field.utcoffset = 2 |
| 105 | }}} |
| 106 | to support European time zone offset for a custom due date field named 'due_date', that holds true POSIX microsecond timestamps (see: [t:wiki:TracDev/Proposals/TracTicketsCustomTimeFields custom time fields proposal]). |
| 107 | |