jira_create_issue
Create a new Jira issue (bug, task, story, epic, or subtask) in a project. Returns the new issue key and URL for tracking.
Instructions
Create a new Jira issue (bug, task, story, epic, subtask, etc.) in a project. Use jira_get_issue_types first if unsure which issue types are available. For subtasks, provide the parentKey. For custom fields, pass customFields keyed by field id or a unique name from jira_get_create_meta (not jira_get_fields). Returns the new issue key and URL.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"projectKey": "<projectKey>",
"issueType": "<issueType>",
"summary": "<summary>"
},
"name": "jira_create_issue"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| labels | No | Labels to add | |
| dueDate | No | Due date in YYYY-MM-DD format | |
| summary | Yes | Issue title/summary - a brief description of the issue | |
| assignee | No | Username to assign the issue to | |
| priority | No | Priority name (e.g., High, Medium, Low) | |
| issueType | Yes | Issue type name (e.g., Bug, Task, Story, Epic, Sub-task). Use jira_get_issue_types to see available types | |
| parentKey | No | Parent issue key for subtasks | |
| components | No | Component names | |
| projectKey | Yes | Project key (e.g., KP). Use jira_get_projects to list available projects | |
| description | No | Issue description | |
| fixVersions | No | Fix version names | |
| customFields | No | Custom fields keyed by field id (e.g. customfield_10006) or a unique name from that issue type's meta. Values are raw Jira REST payloads, not display names. Call jira_get_create_meta for schema/allowedValues and unique names. Examples: number 5, string "text", select {"value":"Yes"}, Server user {"name":"username"}, multi-select [{"value":"A"}], null to clear. Do not call jira_get_fields before create. |