Changes between Version 27 and Version 28 of TracCronPlugin


Ignore:
Timestamp:
Nov 3, 2010 10:44:45 AM (4 years ago)
Author:
tbressure
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • TracCronPlugin

    v27 v28  
    228228}}} 
    229229 
    230 When the daily schedule will trigger the task, the value of the kay will be passed to the '''wake_up''' call. Parameters can be coma separated multiple value. Default is '''empty''' 
     230When the daily schedule will trigger the task, the value of the key will be passed to the '''wake_up''' call. Parameters can be coma separated multiple value. Default is '''empty''' 
    231231 
    232232== Bundled Task == 
    233233 
    234 Beside the HearBeat task provided for testing purprose, TracCronPlugin come with following useful task. 
     234Beside the HearBeat task provided for testing purpose, TracCronPlugin come with following useful task. 
    235235 
    236236=== sleeping_ticket === 
    237237 
    238 This task remind reporter about orphaned ticket and assiged user about sleeping ticket. Orphaned ticket is a ticket in new status since more than a given amount of day. An email notifcation is sent to the reporter in such a case. A sleeping ticket is a ticket assigned to an user, but the user either did not accepet it or did not touch the ticket(make comment for exemple) since more than a gievn amount of day. The assigned user is notified in such a case. The delay is an optional parameter associated with each schedule. Default value is '''3 day'''. 
    239  
     238This task remind reporter about orphaned ticket and assigned user about sleeping ticket. Orphaned ticket is a ticket in new status since more than a given amount of day. An email notification is sent to the reporter in such a case. A sleeping ticket is a ticket assigned to an user, but the user either did not accept it or did not touch the ticket(make comment for example) since more than a given amount of day. The assigned user is notified in such a case. The delay is an optional parameter associated with each schedule. Default value is '''3 day'''. 
     239 
     240=== unreachable milestone === 
     241'''Note''': Since 0.2dev_r9388 
     242This 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 send a mail to user defined with ''unreachable_milestone.recipient'' (default is '''empty''') for each milestone with he 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 near milestone until 3 day ahead. You can change the value with parameter either by setting ''unreachable_milestone.<schedule>.arg'' or in admin panel. 
     243 
     244This is an example of the mail for release manager: 
     245{{{ 
     246Hello, 
     247 
     248The milestone milestone1 is near to be closed. Its due date is 11-30-2010. 
     249 
     250Unfortunately we have detected some still opened ticket. 
     251Please consider to postpone them or ensure they will meet the milestone due date. 
     252 
     253These ticket are 
     254 
     255testing ticket 
     256http://localhost:8000/dummy/ticket/1 
     257 
     258testing ticket 
     259http://localhost:8000/dummy/ticket/3 
     260 
     261 
     262 
     263Best regard. 
     264 
     265-- 
     266My Project <http://localhost:8000/dummy> 
     267My example project 
     268}}} 
    240269 
    241270== Bundled Scheduler ==