As mentioned above, the project data used to create the Gantt charts are stored in Tiki trackers. Create the Tracker with all the specific fields or use this Profile as a template, adjusting it to your own needs. Start with the Plugin Gantt Chart by adding the code to a Wiki page once you have created a tracker.

{ganttchart trackerId="1" name="trackerganttTaskName" begin="trackerganttStartDate" end="trackerganttEndDate" resourceId="trackerganttResponsible" roleId="trackerganttRole" status="trackerganttStatus" progress="trackerganttProgress" canWrite="true" canDelete="true" canWriteOnParent="true" description="trackerganttDescription" code="trackerganttCode" effort="trackerganttEffort" resourceId="trackerganttResourceId"  order="trackerganttOrder" level="trackerganttLevel" depends="trackerganttDependencies"}

The previous code will give the result this overview:

Click to expand

The Gantt Chart Plugin allows you to manage a complete project of any size, to divide it into tasks, to associate resources with each one with its role. When managing the project, you can create a task hierarchy, create dependencies between tasks, determine milestones, highlight the critical path, modify resources, change time scheduling, etc.

To quickly build Gantt charts, use the undo, redo, un-indent task, indent task, move up, move down, delete, EXPAND_ALL, COLLAPSE_ALL, zoom out, zoom in, Print, CRITICAL_PATH, control options to handle the different task display modes, fullscreen, task status color control and the Save button.

With a simple click, set the critical path; remove a task; switch to fullscreen mode, etc.

Click to expand

Organise projects into tasks linked by dependencies

Click to expand

• id: used to synch data with the server. If the id is supplied by the server it will untouched. Tasks created client side will acquire a temporary id starting with “tmp_”
• level: it is the depth (the indentation) of a task in the Gantt structure. The root task is at level 0 (zero), its children at level 1 (one) and so on. Levels must be consistent with the project structure: you can’t have a task of level n+1 if you don’t have a task of level n above on the list
• start, end: are expressed in milliseconds. “start” is set to the first millisecond of the day, “end” is set to the last millisecond of the day.
• duration: is always in working days. If there are holidays on the calendar the end date will take it into account. Actually the end date is always recomputed using “start” and “duration”, and it is supplied for comfort
• startIsMilestone, endIsMilestone: booleans. Once set to true, task’ start/end can’t move accidentally. You always can change dates directly on the task, but not by acting on children or predecessors.
• depends: a string comma delimited containing indexes of tasks on which this task depends. Multiple dependencies are supported. Only the finish-to-start dependency type is supported (other types can be workarounded by introducing intermediary brother tasks or children). It is possible to specify a “lag” in days by using a “:”. E.g.: 7:3,8 means that the task will start 3 days after task 7 is completed and task 8 is completed.
• status: this is a string representing the status of the task. Allowed statuses are: STATUS_ACTIVE, STATUS_DONE, STATUS_FAILED, STATUS_SUSPENDED, STATUS_UNDEFINED. As stated before, task statuses allow to use your project like a sort of workflow: e.g.: if “task b” depends on “task a”, “task b” will remain in “STATUS_SUSPENDED” until “task a” will pass from “STATUS_ACTIVE” to “STATUS_DONE”. For the complete status transition rules see below.
• progress: a number that specifies progress: 0% none 50% half way and so on. In some cases 123% can be a meaningful value for progress, so there are no constraints.

Task statuses are a key feature in this plugin.

When you close some tasks (change status to “completed”) you will see how dependent tasks/children will change their status according to the following rules:

• any status-> STATUS_DONE: may activate dependent tasks, both suspended and undefined. Will set to done all descendants.
• STATUS_FAILED -> STATUS_DONE: do nothing if not forced by hand.
• STATUS_UNDEFINED -> STATUS_ACTIVE: all children become active, if they have no dependencies.
• STATUS_SUSPENDED -> STATUS_ACTIVE : sets to active all children and their descendants that have no inhibiting dependencies.
• STATUS_DONE -> STATUS_ACTIVE: all those that have dependencies must be set to suspended.
• STATUS_FAILED -> STATUS_ACTIVE: nothing happens: child statuses must be reset by hand.
• any status-> STATUS_SUSPENDED: all active children and their active descendants become suspended. when not failed or forced
• any status-> STATUS_UNDEFINED: all active children and their active descendants become suspended. when not failed or forced.
• any status-> STATUS_FAILED: children and dependants are set to failed.

• See Sample Gantt Chart

Added gantt items duplication within same tracker since Tiki23:

• Use ganttId to indicate the value to filter items;
• User ganttIdField to indicate the field perm_name that holds the value above;
• Use canDuplicate to indicate if it can duplicate or not (both ganttId and ganttIdField need to have values)
• When duplicating items, a new ganttId is chosen and also the option to update the existing wikiplugin_ganttchart to display the new duplicated items.
• If user does not have permissions to create new tracker items, the duplication is not available.

• Trackers
• jQuery Gantt editor

• GanttChart

• Gantt Chart
• Gantt
• PluginGantt
• Plugin Gantt
• Plugin GanttChart
• Plugin Gantt Chart