Issue tasks

Up to 100 pieces of work in one call, matched on external_id, which is required here — a task has no natural key of its own, since the same round is issued every week under the same title.

status is not accepted, and neither are the timestamps around it. The product moves a task through its lifecycle with events — completing notifies, approval routes, reopening makes it pastdue again — and a status written straight onto the row fires none of that. Issue the work here; read where it got to with GET /company/v3/tasks.

Eight fields are not accepted either — req_photo, req_sequence, gallery, get_location, get_timing, is_keep_status, req_approve, req_notify. They configure the mobile application, not the job.

Where the work sits is taken from whoever it is for. Omit location_id, department_id and position_id and they come from the assignee — your system knows the person, not our org chart. Send them to override.

items is an exception to the omitted-field rule: sending it replaces the steps outright, because a step carries no key to match an incoming one against — and replacing them discards the completion the person doing the work recorded. Omit the key to leave them alone. managers likewise states who approves now rather than adding to them.

kpi_plan has no "unset" — the column is NOT NULL with a default of 0, so an omitted plan is a plan of zero.