plans

createTask

Create a task in a plan. Requires planId and title. Accepts every field updateTask accepts, so a task can be created complete in ONE call: no create-then-update, and no window in which other actors read a half-written record. Pass parentItemId to create it under its story, requirement or feature in the work hierarchy (which may be in another plan, or in none). Pass fields (for example ["id", "friendlyId", "versionTimestamp"]) for a short answer instead of the whole task.

post/tools/createTask

Request

  • Base URL: https://api.stablebaseline.io/functions/v1/cloud-serve/api/v1
  • URL: https://api.stablebaseline.io/functions/v1/cloud-serve/api/v1/tools/createTask
  • Auth: HTTP bearer

Request body

planIdstring required
titlestring required
phaseIdstring

Phase to assign to.

parentItemIdstring

The work item this one belongs to in the work hierarchy: an epic for a story, a story for its tasks or test cases. Any item in the same project, in any plan or phase. Not the plan outline nesting, which setPlanItemParent sets. Give its UUID or friendly id (such as IMP-12 or TAS-3). Rules: the same project; no loops (an item cannot sit inside its own children); at most 5 levels, counting this item's own children.

descriptionstring
typestring

Type. Default: task, which takes a TAS- id. Override only to put another kind of work item in the plan, for example a user_story (a STY- id) or a test_case (a TC- id); the id's prefix follows the type. Valid values: feature, enhancement, bug, tech_debt, architecture_gap, documentation_gap, risk, epic, user_story, requirement, test_case, spike, task.

status'captured' | 'triaging' | 'shaped' | 'approved' | 'ready_for_agent' | 'in_progress' | 'ready_for_review' | 'in_review' | 'blocked' | 'done' | 'rejected' | 'deferred'

Initial status. Default: captured.

prioritystring

Priority. Default: medium.

urgencystring

e.g. this_week, this_month, this_quarter.

source'human_manual' | 'agent_review' | 'doc_comment' | 'feedback' | 'incident' | 'postmortem' | 'code_review' | 'imported'

Where the work came from. Default: human_manual (shown as a general item), which is right for anything you raise yourself. Use feedback, incident, postmortem, code_review, doc_comment or imported when the item came from one of those. agent_review files the item under Compliance in the register: use it only for a compliance finding.

source_channelstring
category_idstring

Category ID.

problem_statementstring
desired_outcomestring
business_impactstring
user_impactstring
why_nowstring
constraintsstring[]
non_goalsstring[]
impacted_documentsobject[]

Array of {id, title}.

linked_document_idsstring[]

Document IDs to link. Titles resolved automatically.

impacted_diagramsobject[]

Array of {id, name}.

impacted_componentsstring[]
impacted_repositoriesstring[]
agent_readyboolean
agent_missing_infostring[]
agent_recommended_actionstring
agent_complexitystring

low, medium, high, very_high.

agent_confidencenumber

0.00 to 1.00.

agent_briefstring
owner_idstring

User UUID to assign as owner. MUTUALLY EXCLUSIVE with owner_team_id. Use listAssignablePrincipals(projectId, kind='user') to look up valid UUIDs.

owner_team_idstring

Team UUID to assign as owner (assigns the whole team). MUTUALLY EXCLUSIVE with owner_id. Use listTeams or listAssignablePrincipals(kind='team') to look up valid UUIDs.

target_datestring

YYYY-MM-DD.

start_datestring

YYYY-MM-DD.

end_datestring

YYYY-MM-DD.

wbs_codestring
positionnumber
percent_completenumber

Progress percentage (0-100). Null means not tracked.

relationshipsobject

Free-form JSON for logical links: blocks, blocked_by, duplicates, supersedes, relates_to (arrays of item IDs).

metadataobject

Free-form JSON stored alongside the task. On updateTask this MERGES rather than replaces.

fieldsstring[]

Optional. Answer with only these fields instead of the whole task, for example ["id", "versionTimestamp"]. Any of the task's own fields (snake_case or camelCase) or of the keys around it in the full answer (versionTimestamp, href and, where present, url, title, trackingId, message). The id is always returned, and so is any notice that needs your attention (a note, such as a phase's dates following its tasks or an item's id changing with its type, and a date change's cascadePreview). Unknown names are ignored.

Response

Tool result (shape varies per tool — refer to the tool's docs for the exact return value).

object required

Changes

No recorded changes to this operation across all 1 revision of this API.