Docs

Issues

Keys stay readable. Status stays honest. Sub-issues inherit the project.

Create

ParameterTypeDescription
titlerequiredstringWhat needs doing
teamrequiredstringPrefix team (CC)
descriptionstringBody markdown / plain
statusenumbacklog | todo | in_progress | in_review | done | canceled
projectIdstringProject id, key, or slug
assigneeobject{ kind:'person', id } or { kind:'employee', slug }
parentstringParent issue key for a sub-issue
bash
curl -sS -X POST 'https://pm-api.cloudcrew.si/actions/issue_create' \
  -H 'Authorization: Bearer <token>' \
  -H 'Content-Type: application/json' \
  -d '{"title":"Ship intake form","team":"CC","status":"todo","projectId":"CC"}'

Update & close

ParameterTypeDescription
keyrequiredstringIssue key like CC-12
statusenumNew status — may fire automations
titlestringRename
commentstringAdd a comment in the same write
assigneeobject|nullReassign or clear
labelIdsstring[]Replace labels
bash
curl -sS -X POST 'https://pm-api.cloudcrew.si/actions/issue_update' \
  -H 'Authorization: Bearer <token>' \
  -H 'Content-Type: application/json' \
  -d '{"key":"CC-12","status":"done","comment":"Shipped intake form on /ask."}'
Close with a comment that matches the title (what you clicked / saw). Don’t mark done on a stub. issue_delete needs a person OK.