manage_issues
Perform Jira issue operations: create, read, update, delete, assign, transition, comment, link, manage watchers, and more.
Instructions
Unified tool for Jira issue operations. Actions: 'get', 'list_types', 'get_links', 'get_history', 'create', 'update', 'assign', 'transition', 'add_comment', 'edit_comment', 'list_comments', 'delete', 'link', 'list_link_types', 'get_watchers', 'add_watcher', 'remove_watcher', 'move'
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| action | Yes | Action to perform: 'get', 'list_types', 'get_links', 'get_history', 'create', 'update', 'assign', 'transition', 'add_comment', 'edit_comment', 'list_comments', 'delete', 'link', 'list_link_types', 'get_watchers', 'add_watcher', 'remove_watcher', 'move', 'archive', 'unarchive', 'list_transitions', 'add_labels', 'remove_labels' | |
| issue_key | No | Jira issue key (e.g., PROJ-123). Required for most actions | |
| issue_keys | No | Comma-separated issue keys (for 'archive', 'unarchive'). Archiving requires a Jira plan that supports it | |
| project_key | No | Project key (for 'create', 'list_types') | |
| project_id | No | Project ID (for 'list_types' — use project_key or project_id) | |
| summary | No | Issue summary/title (for 'create', 'update') | |
| description | No | Issue description in markdown (for 'create', 'update'). Supports: # headings, **bold**, *italic*, ~~strikethrough~~, [links](url), - bullet lists, 1. numbered lists, > blockquotes, tables, and fenced code blocks. URLs are auto-linked. | |
| issue_type | No | Issue type: Story, Bug, Task, Epic, Sub-task (for 'create') | |
| priority | No | Priority: Highest, High, Medium, Low, Lowest (for 'create', 'update') | |
| assignee_id | No | Assignee account ID (for 'create', 'update', 'assign'). Use 'unassigned' to remove | |
| parent_key | No | Parent/epic issue key. On 'create' sets the parent; on 'update' re-parents the issue (verified by readback - fails loudly if the server ignores it) | |
| labels | No | Comma-separated labels (for 'create', 'update') | |
| components | No | Comma-separated component names (for 'create', 'update') | |
| fix_versions | No | Comma-separated fix version names (for 'create', 'update') | |
| due_date | No | Due date in YYYY-MM-DD format (for 'create', 'update') | |
| transition | No | Target transition name (for 'transition'), e.g. 'In Progress', 'Done' | |
| comment | No | Comment body in markdown (for 'add_comment', 'edit_comment', 'link'). Supports: **bold**, *italic*, ~~strikethrough~~, [links](url), - lists, > blockquotes, and fenced code blocks. URLs are auto-linked. | |
| comment_id | No | Comment ID (required for 'edit_comment') | |
| link_type | No | Link type name (for 'link'), e.g. 'Blocks', 'Duplicate', 'Relates' | |
| inward_key | No | Inward issue key (for 'link') — the issue that IS affected | |
| outward_key | No | Outward issue key (for 'link') — the issue that CAUSES the effect | |
| target_project_key | No | Target project key (for 'move'). Only works with company-managed (classic) projects | |
| target_issue_type | No | Target issue type name (for 'move'), e.g. 'Story', 'Task'. Optional — keeps current type if omitted | |
| start_at | No | Pagination start (for 'list_comments', 'get_history') | |
| max_results | No | Max results to return |