| 21 | | ||Argument ||Version ||Description ||Default |
| 22 | | || `formats`||||What to display in the format control. A pipe-separated list of `minute`, `hour`, `day`, `week`, `month`, and `quarter` (though `minute` may not be very useful). ||`day|week|month|quarter`|| |
| 23 | | || `format`|| ||Initial display format, one of those listed in `formats` || First format || |
| 24 | | || `sample`|| ||Display sample tasks (1) or not (0) || 0 || |
| 25 | | || `res`|| ||Show resource column (1) or not (0) || 1 || |
| 26 | | || `dur`|| ||Show duration colunn (1) or not (0) || 1 || |
| 27 | | || `comp`|| ||Show percent complete column (1) or not (0) || 1 || |
| 28 | | || `caption`|| ||Caption to place to right of tasks: None, Caption, Resource, Duration, %Complete || Resource || |
| 29 | | || `startDate`|| ||Show start date column (1) or not (0) || 1 || |
| 30 | | || `endDate`|| ||Show end date column (1) or not (0) || 1 || |
| 31 | | || `dateDisplay`|| ||Date display format: 'mm/dd/yyyy', 'dd/mm/yyyy', or 'yyyy-mm-dd' || 'mm/dd/yyyy' || |
| 32 | | || `openLevel`|| ||Number of levels of tasks to show. 1 = only top level task. || 999 || |
| 33 | | || `expandClosedTickets`||0.9||Show children of closed tickets (1) or collapse the subtree (0).|| 1 || |
| 34 | | || `colorBy`|| ||Field to use to choose task colors. Each unique value of the field will have a different color task. Other likely useful values are owner and milestone but any field can be used. || priority || |
| 35 | | || `root`|| ||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.|| || |
| 36 | | || `goal`|| 0.9 ||When using something like MasterTickets plugin to maintain ticket dependencies, you may create a Gantt showing a ticket and all of its predecessors with `goal=<ticket#>`. The macro uses the configured `succ` field to find all predecessor tasks and build an `id=` argument for Trac's native query handler.[[br]][[br]]Multiple goals may be provided like `goal=1|12|32`.[[br]][[br]]When used in a ticket description or comment, `goal=self` will display the current ticket's predecessors.|| || |
| 37 | | || `lwidth`|| ||The width, in pixels, of the table of task names, etc. on the left of the Gantt. || || |
| 38 | | || `showdep`||||Show dependencies (1) or not (0)||1|| |
| 39 | | || `userMap`||0.8||Map user IDs to full names (1) or not (0).||1|| |
| 40 | | || `omitMilestones`||0.8||Show milestones for displayed tickets (0) or only those specified by `milestone=` (1)||0|| |
| | 21 | ||'''Argument''' ||'''Version''' ||'''Description''' ||'''Default''' |
| | 22 | || `caption`|| ||Caption to place to right of tasks: None, `Caption`, `Resource`, `Duration`, `%Complete` || `Resource` || |
| | 23 | || `comp`|| ||Show (`1`) percent complete column, or do not (`0`). || `1` || |
| | 24 | || `colorBy`|| ||Field to use to color tasks. Useful fields are `priority`, `owner` and `milestone` but any field can be used. || `priority` || |
| | 25 | || `dur`|| ||Show (`1`) duration colunn, or do not (`0`). || `1` || |
| | 26 | || `dateDisplay`|| ||Format to display dates: `mm/dd/yyyy`, `dd/mm/yyyy`, or `yyyy-mm-dd` || `mm/dd/yyyy` || |
| | 27 | || `endDate`|| ||Show (`1`) end date column, or do not (`0`). || `1` || |
| | 28 | || `expandClosedTickets`||0.9||Show (`1`) children of closed tickets in the task hierarchy or collapse the subtree (`0`). || `1` || |
| | 29 | || `format`|| ||Initial display format, one of those listed in `formats` || `day` || |
| | 30 | || `formats`||||Formats to show for Gantt chart. A pipe-separated list of `minute`, `hour`, `day`, `week`, `month`, and `quarter`. || `day|week|month|quarter` || |
| | 31 | || `goal`|| 0.9 ||Ticket(s) to show predecessors of. When using something like MasterTicketsPlugin to maintain ticket dependencies, you may create a Gantt showing a ticket and all of its predecessors with `goal=<ticket#>`. The macro uses the configured `succ` field to find all predecessor tasks and build an `id=` argument for Trac's native query handler.[[br]][[br]]Multiple goals may be provided like `goal=1|12|32`.[[br]][[br]]When used in a ticket description or comment, `goal=self` will display the current ticket's predecessors.|| None || |
| | 32 | || `hoursPerDay`|| ||Hours worked per day || `8.0` || |
| | 33 | || `lwidth`|| ||Width (in pixels) of left table (The one contains task names, etc. on the left of the Gantt chart.) || None || |
| | 34 | || `omitMilestones`||0.8||Show milestones for displayed tickets (`0`) or only those specified by `milestone=` (`1`). || `0` || |
| | 35 | || `openLevel`|| ||How many levels of task hierarchy to show open. `1` = only top level task. || `999` || |
| | 36 | || `res`|| ||Show (`1`) resource column, or do not (`0`). || `1` || |
| | 37 | || `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 || |
| | 38 | || `sample`|| ||Display (`1`) sample tasks in Gantt, or do not (`0`) || `0` || |
| | 39 | || `schedule`|| ||Schedule algorithm: as-last-as-possible (`alap`) or as-soon-as-possible (`asap`) || `alap` || |
| | 40 | || `showdep`|| ||Show (`1`) dependencies in Gantt, or do not (`0`). || `1` || |
| | 41 | || `startDate`|| ||Show (`1`) start date column, or do not (`0`). || `1` || |
| | 42 | || `userMap`||0.8||Map (`1`) user IDs to full names, or do not (`0`). || `1` || |
