Skip to content
Release: Australia · Updated: 2026-03-12 · Official documentation · View source

Important planned task table fields

The Planned Task table has these fields.

LabelNameTypeDescription
Actual costwork_costcurrencyThe actual cost of the planned task, to be compared with the Estimated cost.
Actual durationwork_durationglide_durationThe actual length of time (from start time to end time) of work on the planned task, to be compared with the Planned duration.
Actual effortwork_effortglide_durationThe actual time spent working, to be compared to the Planned effort.
Critical Pathcritical_pathboolean 
Estimated costcostcurrencyAn estimation of the cost of the planned task, to be compared with the actual cost.
HTML Descriptionhtml_descriptionhtmlA description field that accepts HTML mark-up.
Percent Completepercent_completedecimalA percentage of the completed effort. Generated using the Planned effort and Actual effort fields.
Planned durationdurationglide_durationThe estimated length of time (from start time to end time) of the planned task.
Planned efforteffortglide_durationThe estimated amount of time spent working on the planned task.
Planned end dateend_dateglide_date_timeThe estimated date and time for the planned task to end.
Planned start datestart_dateglide_date_timeThe estimated date and time for the planned task to start.
Remaining durationremaining_durationglide_durationThe difference in planned and actual duration, representing the time left for the planned task.
Remaining effortremaining_effortglide_durationThe difference in planned and actual effort, representing the amount of work time left for the planned task.
RolluprollupbooleanRead-only field managed by the system that identifies the task as having child tasks. A rollup task has several its fields calculated from the children so those fields are read-only.
Time constrainttime_constraintstringA description of time constraints that apply to the planned task.
Top Tasktop_taskreference (planned_task)When different planned tasks are stacked in a hierarchy, this field populates with the highest-level parent task. For example, if Project A has a child Project B, and Project B has a child Project C, then the Top Task for Project C is Project A. The Top Task field for Project A is blank.
Actual start datework_startglide_date_timeThe actual date when the work starts on the planned task.
Actual end datework_endglide_date_timeThe actual date when the work ends on the planned task.

Parent Topic:Extending the Task table with Planned tasks