Create issue
jira_create_issueCreate Jira issues with summaries, fields, and light Markdown descriptions, routed to the correct instance by project key mapping or an explicit instance.
Instructions
Create an issue. The description accepts light Markdown (headings, lists, bold, code, links, code fences) and is converted to the format the instance expects. The instance is routed by project key mapping or the 'instance' argument.
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": {
"summary": "<summary>"
},
"name": "jira_create_issue"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| labels | No | ||
| parent | No | Parent issue key (sub-tasks, or epics on team-managed projects). | |
| boardId | No | Use the project of this agile board. | |
| dueDate | No | YYYY-MM-DD | |
| project | No | Project key. Defaults to the parent's project, the board's project or the instance defaultProject. | |
| summary | Yes | ||
| assignee | No | 'me', email, accountId (Cloud) or username (Data Center). | |
| instance | No | Jira instance name (see jira_list_instances). Optional: calls are routed automatically by 'name:KEY' prefixes, issue URLs, project-key mapping, the default instance, or when only one instance exists. | |
| priority | No | Priority name, e.g. 'High'. | |
| issueType | No | Issue type name (default 'Task'). Use 'Sub-task' with parent. | |
| components | No | Component names. | |
| description | No | ||
| customFields | No | Extra raw Jira fields, e.g. {"customfield_10016": 5}. Values are sent as-is. |