Skip to main content

​
Description

Task objects represent discrete units of work or activities that need to be performed to achieve a specific objective. In a project management and systems engineering context, tasks have defined durations, start and end dates, and may depend on other tasks or require resources. They are the building blocks of project schedules and work breakdown structures.
Model Task objects are schedule-modeling elements stored with the project. They are distinct from operational Task Cards used for issues, assignees, tags, and team-board workflow. In agent workflows, use the Schedule toolbox for model Task objects and the Cards toolbox for Task Cards.
Tasks support prerequisite relationships with other tasks, allowing you to define dependencies where one task must complete before another can begin. Prerequisites can include time offsets, enabling flexible scheduling such as “start 2 days after Task A completes.” The duration field specifies how long a task takes to complete, with configurable units (Days, Hours, etc.). Tasks automatically calculate their start and end dates based on their duration, prerequisites, and the project timeline. The ordering of tasks is based on the ordering in the index. To change top to bottom ordering of tasks in the Gantt view rearrange the tasks using the index.
If the task has owned sub tasks as children, then the parent task will inherit the start and end date of its children and is not editable.
Use the properties view to edit the start/ end dates or durations. To view tasks in context use the Gantt view. Can also edit duration and dates from the Gantt view as well.

​
View Types

​
Properties Fields

​
boolean
Yes. Tasks can be used as bases or specializations through object inheritance.
​
string
Name of the object.
​
string
Short name of the object.
​
string
Description of the object.
​
object
Attributes store task-local planning parameters and calculated values. Constraints define rules that the task schedule or execution must satisfy.Read more about Attributes and Constraints.
​
object
Executable Code objects owned by the task for scheduled automation or task-specific implementation.Read more about Code
​
string
The start date of the task. Can be specified as a date string or calculated based on prerequisites and project timeline.
​
string
The end date of the task. Can be specified as a date string or calculated based on the start date and duration.
​
object
The duration of the task, consisting of:
  • value: The numeric duration value (string)
  • unit: The time unit (default: “Days”)
  • kind: The value type (default: “number”)
Duration is used to calculate the end date when a start date is known, or vice versa.
​
object
A record of prerequisite tasks that must complete before this task can begin. Each prerequisite is keyed by the task ID and contains:
  • offset: Time offset after the prerequisite completes (string)
  • offsetUnit: Unit for the offset (default: “Days”)
  • offsetKind: Type of offset value (always “number”)
Prerequisites enable dependency chains where tasks wait for other tasks to complete, optionally with a time delay.
​
object
A list of all sub-task objects owned by this task.Sub-tasks can be viewed and deleted.Read more about Tasks
​
connection
A list of all Relationships this object has with other model objects.Read more about Relationships