The TaskJuggler Manual
Prev	Chapter 7. Property Reference	Next

... ]

columns <`columnid`> [, <`columnid`> ... ]
Description	Specifies which columns shall be included in a report. All columns support macro expansion. Contrary to the normal macro expansion, these macros are expanded during the report generation. So the value of the macro is being changed after each table cell or table line. Consequently only build in macros can be used. To protect the macro calls against expansion during the initial file processing, the report macros must be prefixed with an additional `$`.
Attributes	Name	Type	Description
Attributes	`columnid`	ID	See table below for possible values.
Optional Attributes	celltext, cellurl, hidecelltext, hidecellurl, subtitle, subtitleurl, title, titleurl
Context	csvaccountreport, csvresourcereport, csvtaskreport, htmlaccountreport, htmlmonthlycalendar, htmlresourcereport, htmltaskreport, htmlweeklycalendar, resourcereport, taskreport,
Inheritable	No	Scenario Spec.	No

`accounts`	This columns lists the account that is assigned to the respective task. It is called 'accounts' because later versions will have support for multiple accounts.
`chart`	Use this column to get Gantt and resource charts. It's only supported by the interactive reports in the GUI.
`completed`	The percentage the task has been completed already. This is either the value specified by complete or a value computed according to the current date (or the date specified by now) and the length, duration or effort.
`completedeffort`	The effort of a task that has already been completed.
`cost`	The accumulated costs of the task and its sub tasks
`criticalness`	The criticalness of the task. It is a measure for the probability that an effort task gets the requested resources early.
`daily`	A day-by-day calendar view of the tasks
`depends`	The task index of the tasks on which this task depends
`duration`	The duration of the task
`efficiency`	The efficiency of the resource. It's a measurement of how much the resource can contribute to the workload of tasks.
`effort`	The effort put into the task
`end`	The end date of a task
`endbuffer`	The percentage of the endbuffer
`endbufferstart`	The start time of the end buffer
`flags`	The list of flags assigned to the task or resource
`follows`	The task index of the tasks that depend on this task
`freeload`	The workload of the resource that has not been allocated.
`hierarchindex`	The hierarchical index of a task. The index is calculated from the hierarchical structure of the list as well as the start and end dates.
`hierarchno`	The hierarchical number of a task. It is based on the order of declaration.
`id`	The global ID of a task
`index`	The index of a task. The index is calculated from the hierarchical structure of the list as well as the start and end dates.
`maxeffort`	The maximum daily load wanted for the resource
`maxend`	The latest desired end date
`maxstart`	The latest desired start date
`mineffort`	The minimum daily load wanted for the resource
`minend`	The earliest desired end date
`minstart`	The earliest desired start date
`monthly`	A month-by-month calendar view of the tasks
`name`	The name of a task, resource, or account
`no`	The task index in the list. It starts with 1 and increases for every listed item by 1.
`note`	The description of the task
`pathcriticalness`	The overall criticalness of the task. It is a measure for the probability that an effort task gets scheduled as early as possible. The tasks of the most critical path have the highest path criticalness.
`priority`	The scheduling priority
`profit`	The accumulated profit of the task and its sub tasks
`projectid`	The project ID of the task
`projectids`	The project IDs of the projects a resource is allocated to
`quarterly`	A quarter-by-quarter calendar view of the tasks
`rate`	The daily rate of the resource
`reference`	A reference to a URL that contains further information.
`remainingeffort`	The effort of a task that still needs to be done to complete the task..
`resources`	The names of the used resources
`responsibilities`	A list of all tasks indices for which a resource is responsible
`responsible`	The name of the resource responsible for a task
`revenue`	The accumulated revenue of the task and its sub tasks
`scenario`	The name of the scenario. This column is helpful when multiple scenarios are shown in the table. See also scenarios.
`schedule`	A detailed schedule of the allocations for the resource.
`scheduling`	The scheduling direction of the task. ASAP (As Soon As Possible) tasks are scheduled from start to end, ALAP (As Late As Possible) are scheduled from end to start.
`seqno`	The task index in the order of declaration. Each time a task declaration is completed, the sequence number is increased by 1.
`start`	The start date of a task
`startbuffer`	The percentage of the start buffer
`startbufferend`	The end time of the start buffer
`status`	The current status of the task. This is derived from the current date or the date specified by now and the degree of completion. The degree of completion is either computed or has been specified by complete.
`statusnote`	Some comment about the current status of the task.
`total`	Total accumulated values
`utilization`	The ratio between the allocated work load of the resource and it's overall available work load.
`weekly`	A week-by-week calendar view of the tasks
`yearly`	A year-by-year calendar view of the tasks

The following macros are supported for normal table cells:

`$${0}`	This is the original value of the table cell. This macro is useful if the user would like to extend the cell text with a fixed string.
`$${accountid}`	The ID of the account.
`$${resourceid}`	The ID of the resource.
`$${taskid}`	the id of the task.

Additionally the original contents of other cells of the same report line can be accessed by the column ID. The following columns are supported:

index, no, hierarchindex, hierarchno, id, name

For the title or sub title of the calendar columns (daily, weekly, monthly, quarterly, yearly) the following macros are supported:

$${day}, $${month}, $${week}, $${quarter}, $${year}.

project prj  "Project" "1.0" 2005-01-01 - 2005-03-01

resource r "Resource"

task t "Task" {
  task s "SubTask" {
    start 2005-01-01
    effort 5d
    allocate r
  }
}

# Just a very basic report with some standard columns
htmltaskreport "SimpleReport.html" {
  columns hierarchindex, name, start, end, weekly
}

# Report with custom colum title
htmltaskreport "CustomTitle.html" {
  columns hierarchindex, name { title "Work Item" }, effort
}

# Report with custom colum title and subtitle
htmltaskreport "CustomSubTitle.html" {
  columns hierarchindex, name,
          monthly { title " " subtitle "$${month} $${year}" }
  loadunit days
}

# Report with efforts only for leaf tasks 
htmltaskreport "LeafEfforts.html" {
  columns hierarchindex, name,
          effort { hidecelltext ~isLeaf() }
}

# Report with link in title of calendar
htmltaskreport "LinkURL.html" {
  columns hierarchindex, name,
          monthly { subtitleurl "Monthly-Detail-$${month}.html" }
}

# Report with link to page with furter task details
htmltaskreport "LinkToTaskDetails.html" {
  columns hierarchindex,
          name { cellurl "TaskDetails-$${taskid}.html"
                 hidecellurl ~isLeaf() }, start, end
}

# Report with index and task name combined in one single column
htmltaskreport "CombinedColumn.html" {
  columns name { celltext "$${hierarchno} $${0}"}, start, end, weekly
}

Prev	Home	Next
cellurl <`url`>	Up	complete <`percent`>

columns <columnid> [, <columnid> ... ]

columns <`columnid`> [, <`columnid`> ... ]