| << tagfile << | Table Of Contents | >> task (statussheet) >> |
| Keyword | task |
| Purpose | Tasks are the central elements of a project plan. Use a task to specify the various steps and phases of the project. Depending on the attributes of that task, a task can be a container task, a milestone or a regular leaf task. The latter may have resources assigned. By specifying dependencies the user can force a certain sequence of tasks. Tasks have a local name space. All IDs must be unique within the tasks that belong to the same enclosing task. |
|
| Syntax | task [<id>] <name> [{ <attributes> }] |
|
| Arguments | id [ID] | An optional ID. If you ever want to reference this property, you must specify your own unique ID. If no ID is specified, one will be automatically generated. These IDs may become visible in reports, but may change at any time. You may never rely on automatically generated IDs. |
| name [STRING] | The name of the task |
|
| Context | properties, task, supplement (task) | |
| Attributes | Name | Scen. spec. | Inh. fm. Global | Inh. fm. Parent |
| adopt (task) | ||||
| allocate | x | x | ||
| booking (task) | x | |||
| charge | x | |||
| chargeset | x | x | ||
| complete | x | |||
| depends | x | x | ||
| duration | x | |||
| effort | x | |||
| effortdone | x | |||
| effortleft | x | |||
| end | x | |||
| fail | x | |||
| flags (task) | x | x | ||
| journalentry | ||||
| length | x | |||
| limits (task) | x | |||
| maxend | x | x | ||
| maxstart | x | |||
| milestone | x | |||
| minend | x | |||
| minstart | x | x | ||
| note (task) | ||||
| period (task) | x | |||
| precedes | x | x | ||
| priority | x | x | x | |
| projectid (task) | x | x | x | |
| purge | ||||
| responsible | x | x | ||
| scheduled | x | x | ||
| scheduling | x | |||
| schedulingmode | x | |||
| shifts (task) | x | x | ||
| start | x | |||
| supplement (task) | ||||
| task | ||||
| warn | x |
| << tagfile << | Table Of Contents | >> task (statussheet) >> |