Changes between Version 37 and Version 38 of TracJsGanttPlugin


Ignore:
Timestamp:
Nov 8, 2012 10:15:50 PM (23 months ago)
Author:
ChrisNelson
Comment:

Notes about pred-succ and parent-child relations.

Legend:

Unmodified
Added
Removed
Modified
  • TracJsGanttPlugin

    v37 v38  
    3737|| `openLevel`|| ||How many levels of task hierarchy to show open.  `1` = only top level task.  ||  `999`  || 
    3838|| `res`|| ||Show (`1`) resource column, or do not (`0`). ||  `1`  || 
    39 || `root`|| ||Ticket(s) to show descendants of. When using something like Subtickets plugin to maintain a tree of tickets and subtickets, you may create a Gantt showing a ticket and all of its descendants with `root=<ticket#>`.  The macro uses the configured `parent` field to find all descendant tasks and build an `id=` argument for Trac's native query handler.[[br]][[br]]Multiple roots may be provided like `root=1|12|32`.[[br]][[br]]When used in a ticket description or comment, `root=self` will display the current ticket's descendants.||  None  || 
     39|| `root`|| ||Ticket(s) to show descendants of. When using something like Subtickets plugin to maintain a tree of tickets and subtickets, you may create a Gantt showing a ticket and all of its descendants with `root=<ticket#>`.  The macro uses the configured `parent` field or `parentchild` relation to find all descendant tasks and build an `id=` argument for Trac's native query handler.[[br]][[br]]Multiple roots may be provided like `root=1|12|32`.[[br]][[br]]When used in a ticket description or comment, `root=self` will display the current ticket's descendants.||  None  || 
    4040|| `sample`|| ||Display (`1`) sample tasks in Gantt, or do not (`0`) ||  `0`  || 
    4141|| `schedule`|| ||Schedule algorithm: as-last-as-possible (`alap`) or as-soon-as-possible (`asap`) ||  `alap`  || 
     
    150150  fields.succ = blocking 
    151151 
     152  # Alternatively, configure a pred-succ relation like: 
     153  #    relation.pred-succ = mastertickets,source,dest 
     154  # This causes TracPM to query the mastertickets table rather than 
     155  # parse blockedby and blocking custom fields.  This can be somewhat 
     156  # faster. 
     157 
     158 
    152159  # To work with SubticketsPlugin for parent/child relationships,  
    153   ## Ticket field to use as the data source for the parent  
     160  # Ticket field to use as the data source for the parent  
    154161  fields.parent = parents 
    155    
     162 
     163  # Alternatively, configure a parent-child relation like: 
     164  #    relation.parent-child = subtickets,parent,child 
     165  # This causes TracPM to query the subtickets table rather than parse  
     166  # the `parents` custom field.  This can be somewhat faster. 
     167  # When using SubticketsPlugin via a parent-child relation, do not  
     168  # configure a parent_format (next). 
     169 
     170  
    156171  # To work with ChildTickets plugin parent_format, '#%s', 
    157172  # Format of ticket IDs in parent field (default: %s). 
     
    159174   
    160175  # Custom fields for start and due dates 
    161   ## Ticket field to use as the data source for start date (default: None) 
     176  # Ticket field to use as the data source for start date (default: None) 
    162177  fields.start = userstart 
    163   ## Ticket field to use as the data source for finish date (default: None) 
     178  # Ticket field to use as the data source for finish date (default: None) 
    164179  fields.finish = userfinish 
    165180   
     
    182197  estimate_pad = 0.0 
    183198}}} 
    184    * See [#Configuration configuration details] below for explanations and more options. 
     199   * See [#Configurationdetails configuration details] below for explanations and more options. 
    185200   * Additionally, site-wide defaults for macro arguments may be set at [trac-jsgantt] section. More details about them see [#Arguments #Arguments section]. 
    186201{{{