Issue Management Tools

Create, update, and delete work items.

These tools handle the full lifecycle of issues — from creation through updates to deletion. All write operations support semantic matching, so you can reference tickets by description instead of key.

create_epic

Creates a new epic in your project tracker. Epics are the highest-level work items, typically representing a feature or initiative.

When it runs: Called when you ask to create a new epic or feature.

Example trigger: "Create an epic for the new billing system"

Parameter	Type	Required	Description
title	string	Yes	Epic title
description	string	No	Detailed description of the epic

create_task

Creates a story or task, optionally linked to an epic. This is the most common creation tool.

When it runs: Called when you ask to create a task, story, or ticket.

Example trigger: "Create a task for adding rate limiting to the API"

Parameter	Type	Required	Description
title	string	Yes	Task title
description	string	No	Task description
epic_key	string	No	Parent epic key or natural language reference
type	string	No	Issue type (e.g., Story, Bug, Task)
priority	string	No	Priority level (use get_priorities to see available values)
assignee	string	No	Display name of the assignee
labels	string[]	No	Labels to apply

create_subtask

Creates a subtask under a parent issue. Subtasks are the smallest unit of work.

When it runs: Called when you ask to create a subtask or break down a task further.

Example trigger: "Add a subtask to the login story for input validation"

Parameter	Type	Required	Description
title	string	Yes	Subtask title
parent_key	string	Yes	Parent issue key or natural language reference
description	string	No	Subtask description

update_task

Updates any field on a task: status, title, description, assignee, priority, labels, epic link, or adds a comment. All fields are optional except issue_key. This is also the primary tool for adding comments to any ticket.

When it runs: Called when you ask to update, change, move, or comment on a task.

Example trigger: "Mark the auth task as done and add a comment that JWT is implemented"

Parameter	Type	Required	Description
issue_key	string	Yes	Issue key or natural language reference
status	string	No	New status (use get_statuses to see available values)
title	string	No	New title
description	string	No	New description
comment	string	No	Comment to add
assignee	string	No	New assignee display name
priority	string	No	New priority
labels	string[]	No	New labels (replaces existing)
epic_key	string	No	Link to a different epic

update_epic

Updates an epic's status, title, description, or adds a comment.

When it runs: Called when you ask to update or comment on an epic.

Example trigger: "Update the billing epic status to done"

Parameter	Type	Required	Description
epic_key	string	Yes	Epic key or natural language reference
status	string	No	New status
title	string	No	New title
description	string	No	New description
comment	string	No	Comment to add

delete_issue

Permanently deletes any ticket from your project tracker. This cannot be undone.

When it runs: Called when you explicitly ask to delete a ticket.

Example trigger: "Delete the duplicate login task"

Parameter	Type	Required	Description
issue_key	string	Yes	Issue key or natural language reference

get_tasks

Fetches open tasks from the project. Optionally filter by epic to see only tasks belonging to a specific feature.

When it runs: Called when you ask to see tasks, list work items, or check what's open.

Example trigger: "Show me all open tasks for the auth epic"

Parameter	Type	Required	Description
epic_key	string	No	Filter by epic key or natural language reference