create-work-item-tool

Creates a new work item in a project. The issue key (e.g. ACM-123) is generated automatically from the project's customer code. Reasonable defaults are used when optional fields are omitted: the first ordered workflow status becomes the starting status, the first ordered work type becomes the work type, and the reporter defaults to the authenticated user.

Inputs

Name	Type	Required	Description
`project_id`	integer	yes	Project the work item belongs to.
`title`	string	yes	Work item title (max 255 characters).
`description`	string	no	Optional HTML/Markdown description.
`priority`	string	no	`highest`, `high`, `normal`, `low`, `lowest`.
`due_date`	string (`Y-m-d`)	no	Optional due date.
`estimation`	integer	no	Original estimate in minutes.
`remaining_estimate`	integer	no	Remaining estimate in minutes.
`work_type_id`	integer	no	Work type ID. Defaults to the first ordered work type.
`workflow_status_id`	integer	no	Starting status. Defaults to the workflow's first ordered status.
`deadline_id`	integer	no	Linked deadline.
`assignee_id`	integer	no	Assignee user ID.
`sprint_id`	integer	no	Sprint to place the item in. Omit for the backlog.
`parent_id`	integer	no	Parent work item ID for sub-items.

Permissions

project_management::manage_work_items (entry permission).
The user must also be allowed to manage the WorkItem class by WorkItemPolicy.

Example

{
  "project_id": 3,
  "title": "Wire up Sentry releases",
  "priority": "medium",
  "estimation": 120
}

Response

Returns the full work item snapshot (same shape as get-work-item-by-key-tool).

Errors

An unknown project_id returns a validation error.
A project with no configured workflow statuses returns a validation error (workflow_status_id).
A tenant with no work types configured returns a validation error (work_type_id).
A caller without project_management::manage_work_items receives an authorization error.