Creates tasks in projects.
create-tasks
data (Required). It is an array of task
fields. For example, in case the data format is XML, you should
post something like this:
<data>
<item> <!-- create tasks -->
<project_id>100</project_id>
<summary>Task #1</summary>
<detail>This is the task description</detail>
<parent_id>12345</parent_id>
<priority>2</priority>
<plan_start>2008-09-02T08:00:00</plan_start>
<plan_finish>2008-09-04T17:00:00</plan_finish>
<assignments>10001/20%,100010/40h</assignments>
<type_id>1</type_id>
<state_id>1290</state_id>
</item>
<item>
<project_id>100</project_id>
<summary>Task #2</summary>
<detail>This is the task description</detail>
<parent_id>12345</parent_id>
<plan_start>2008-09-03T08:00:00</plan_start>
<plan_finish>2008-09-04T17:00:00</plan_finish>
<assignments>10001/50%</assignments>
<type_id>1</type_id>
<state_id>1291</state_id>
</item>
</data>In case of JSON, you should submit an array of objects with the same properties.
Here are the details of the fields:
project_id (Required). Integer. ID of the
project in which the task is to be added
summary (Required). A short description
of the task.
plan_start (Required). Date. The planned
start date of this task.
plan_finish (Required). Date. The panned
finish date of this task.
parent_id (Optional). Integer. ID of the
parent task.
priority (Optional). Integer between 1
(Very High) and 5 (Very Low)
detail (Optional). A detailed description
for this task.
assignments (Optional). A string of the
form
<user-id-1>/<allocation-1>,<user-id-2>/<allocation-2>,
etc. E.g. 10001/20%,100010/40h
type_id (Optional). Number. The task type
ID.
state_id (Optional). Number. The state
associated with the task type.
can_fill_time (Optional). Boolean.
Whether time can be filled against this task.
budget (Optional). Number. The budget for
this task.
est_non_labor_cost (Optional). Number.
The estimated non-labor cost (a.k.a material cost) for this
task.
fixed_cost (Optional). Number. The fixed
cost for this task.
Nothing