Changes between Version 48 and Version 49 of TracCronPlugin
- Timestamp:
- Jan 17, 2016, 4:31:57 PM (8 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracCronPlugin
v48 v49 11 11 * Bundled out-of-the-box task 12 12 * Scheduler are plugin 13 * Bundled out-of-the-box scheduler '''new''' ''cron syntax is supported''13 * Bundled out-of-the-box scheduler; '''new''': cron syntax is supported 14 14 * Listener mechanism to be notified of task execution 15 * Bundled out-of-the-box listener '''new''' ''admin panel for listener''16 * Task execution history '''new''' ''rss feed is available''15 * Bundled out-of-the-box listener; '''new''': admin panel for listener 16 * Task execution history; '''new''': rss feed is available 17 17 18 18 The plugin provides an administration panel to help with scheduling: … … 31 31 32 32 Current stable release is '''0.3.1'''. 33 33 34 You can use easy_install or pip to download and install the latest package into your Python environment: 34 35 {{{#!sh … … 117 118 118 119 The plugin can be entirely configured from either trac.ini or the administration panel. 119 The section name of TracCronPlugin is traccron, here is a full sample:120 The section name of TracCronPlugin is `traccron`, here is a full sample: 120 121 121 122 {{{#!ini … … 137 138 === Global settings 138 139 139 This control the object called tickerwhich is the thread that launches tasks. If False, no ticket (no thread) is created, so your Trac behaves like there is no cron installed. This is the global setting you can act on to enable or disable all tasks. Default value is '''True''':140 This controls the object called ticker, which is the thread that launches tasks. If False, no ticket (no thread) is created, so your Trac behaves like there is no cron installed. This is the global setting you can act on to enable or disable all tasks. Default value is '''True''': 140 141 141 142 {{{#!ini … … 175 176 }}} 176 177 177 This scheduler triggers a task that needs to be executed once a month. Provide the day in month and the hour when the task will be launched. The day is the index of the day starting at 1. Accepts comma separated value . Default is no value:178 This scheduler triggers a task that needs to be executed once a month. Provide the day in month and the hour when the task will be launched. The day is the index of the day starting at 1. Accepts comma separated values. Default is no value: 178 179 179 180 {{{#!ini … … 214 215 215 216 This task reminds the reporter about orphaned tickets and the assigned user about sleeping tickets. 216 * An orphaned ticket is a ticket with status New sincemore than a given amount of days. An email notification is sent to the reporter in such a case.217 * A sleeping ticket is a ticket assigned to a n user, but the user either did not accept it or did not touch the ticket (add a comment for example) since more than a given amount of day. The assigned user is notified in such a case.217 * An orphaned ticket is a ticket with status New for more than a given amount of days. An email notification is sent to the reporter in such a case. 218 * A sleeping ticket is a ticket assigned to a user, but the user either did not accept it or did not touch the ticket (added a comment for example) for more than a given amount of days. The assigned user is notified in such a case. 218 219 219 220 The delay is an optional parameter associated with each schedule. Default value is '''3 days'''. … … 223 224 '''Note''': Since 0.2dev_r9388 224 225 225 This task scan still opened tickets in near milestone. Such a situation means that those tickets will probably not be part of the milestone. The task sends a mail to user defined with ''unreachable_milestone.recipient'' (default is '''empty''') for each milestone with the list of still opened tickets. You may want to set the value to the release manager user. Reporter and owner are notified too, but only for their tickets. The task looks for the nearest milestone until '''3 days ahead'''. You can change the value with parameter either by setting ''unreachable_milestone.<schedule>.arg'' or inadmin panel.226 This task scans still opened tickets in near milestone. Such a situation means that those tickets will probably not be part of the milestone. The task sends a mail to user defined with ''unreachable_milestone.recipient'' (default is '''empty''') for each milestone with the list of still opened tickets. You may want to set the value to the release manager user. Reporter and owner are notified too, but only for their tickets. The task looks for the nearest milestone until '''3 days ahead'''. You can change the value with parameter either by setting ''unreachable_milestone.<schedule>.arg'' or in the admin panel. 226 227 227 228 This is an example of the mail for release manager: … … 255 256 '''Note''': since 0.2dev_r9390. 256 257 257 Trac allows the administrator to postpone still opened ticket in a given milestone when he closes this milestone. But this is not mandatory. The auto postpone task will help to not forget opened tickets in closed milestone. The task look for such tickets and postponethem in the more recent still opened milestone. Milestone must have a due date.258 Trac allows the administrator to postpone still opened ticket in a given milestone when he closes this milestone. But this is not mandatory. The auto postpone task will help to not forget opened tickets in a closed milestone. The task looks for such tickets and postpones them in the more recent still opened milestone. Milestone must have a due date. 258 259 259 260 === Ticket deadline task … … 261 262 '''Note''': since 0.3. 262 263 263 This task notifies to the ticket's reporter and owner when its ticket is near the deadline as a custom field. You can add a date field for ticket using [http://trac-hacks.org/wiki/DateFieldPlugin DateFieldPlugin]. Besides scheduler settings, there are the following options to configure whenDateFieldPlugin is used:264 This task notifies to the ticket's reporter and owner when its ticket is near the deadline as a custom field. You can add a date field for ticket using the DateFieldPlugin. Besides scheduler settings, there are the following options to configure when the DateFieldPlugin is used: 264 265 265 266 - days_before: notify days before the deadline … … 269 270 [[Image(ticket-with-duedate.png)]] 270 271 271 Here is a sample configuration for t rac.ini:272 Here is a sample configuration for the `trac.ini` file: 272 273 273 274 {{{#!ini