Important planned task table fields

  • Release version: Yokohama
  • Updated January 30, 2025
  • 1 minute to read

    • The Planned Task table has these fields.

    Table 1. Important Planned Task Table Fields
    Label Name Type Description
    Actual cost work_cost currency The actual cost of the planned task, to be compared with the Estimated cost.
    Actual duration work_duration glide_duration The actual length of time (from start time to end time) of work on the planned task, to be compared with the Planned duration.
    Actual effort work_effort glide_duration The actual time spent working, to be compared to the Planned effort.
    Critical Path critical_path boolean
    Estimated cost cost currency An estimation of the cost of the planned task, to be compared with the actual cost.
    HTML Description html_description html A description field that accepts HTML mark-up.
    Percent Complete percent_complete decimal A percentage of the completed effort. Generated using the Planned effort and Actual effort fields.
    Planned duration duration glide_duration The estimated length of time (from start time to end time) of the planned task.
    Planned effort effort glide_duration The estimated amount of time spent working on the planned task.
    Planned end date end_date glide_date_time The estimated date and time for the planned task to end.
    Planned start date start_date glide_date_time The estimated date and time for the planned task to start.
    Remaining duration remaining_duration glide_duration The difference in planned and actual duration, representing the time left for the planned task.
    Remaining effort remaining_effort glide_duration The difference in planned and actual effort, representing the amount of work time left for the planned task.
    Rollup rollup boolean Read-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 constraint time_constraint string A description of time constraints that apply to the planned task.
    Top Task top_task reference (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 date work_start glide_date_time The actual date when the work starts on the planned task.
    Actual end date work_end glide_date_time The actual date when the work ends on the planned task.