Skip to main content
PATCH
Update a project task
Changes a task’s title, description, priority or tags. The body is strict: id plus at least one field. Omitted fields are unchanged and nothing is cleared; tags replaces the stored list. Authority is decided at the task’s project home: 404 unless the caller holds projects:read there, 403 without projects:manage there. The credential’s scopes must include projects:read as well as projects:manage, because the success returns the task; otherwise 403 naming projects:read, and nothing is written. Success is 200 with the post-write ProjectTaskDetail. Only a project’s ordinary tasks are here. A factory task is read and changed through the factory task operations, and a task with no project is never returned. Assigning a task is done by a person in Console.

Authorizations

Authorization
string
header
required

An External App: the JWT it obtains from POST /oauth/token with OAuth2 client_credentials. Pass as Authorization: Bearer <jwt>. An app's static companion key also authenticates as the app, but is deprecated and is not protected by Idempotency-Key.

Headers

Idempotency-Key
string

Optional logical intent key. A same-key retry within 24 hours returns the recorded result without writing again.

Required string length: 1 - 255

Path Parameters

taskId
string
required

The task ID, as GET /api/v2/projects/getTask returns it.

Minimum string length: 1

Body

application/json

The task fields to change; omitted fields are unchanged and nothing is cleared. At least one field besides id is required. Unknown fields are refused.

title
string

The task title, 1 to 200 characters, stored exactly as sent.

Required string length: 1 - 200
description
string

Up to 20,000 characters.

Maximum string length: 20000
priority
enum<string>
Available options:
low,
medium,
high,
urgent
tags
string[]

Up to 20 tags of 1 to 64 characters; replaces the stored list.

Maximum array length: 20
Required string length: 1 - 64

Response

Success

data
object
required
meta
object
required