create_issue
Create Jira issues with full field support, including parent, fix versions, dates, assignee, priority, labels, components, story points, and custom fields.
Instructions
Create a Jira issue with full field support including parent, fixVersions, dates.
Args: project: Project key (e.g., "KAN") issue_type: Issue type name (e.g., "Task", "Story", "Bug", "Epic") summary: Issue title description: Plain text description (supports Jira wiki markup for rich text) assignee_id: Atlassian account ID of assignee priority: Priority name (e.g., "High", "Medium", "Low") labels: List of label strings parent: Parent issue key for sub-tasks or stories under epics (e.g., "KAN-1") fix_versions: List of version names (e.g., ["v1.0.0"]) components: List of component names start_date: Start date in YYYY-MM-DD format due_date: Due date in YYYY-MM-DD format story_points: Story point estimate custom_fields: Dict of custom field IDs to values
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": {
"project": "<project>",
"issue_type": "<issue_type>",
"summary": "<summary>"
},
"name": "create_issue"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| labels | No | ||
| parent | No | ||
| project | Yes | ||
| summary | Yes | ||
| due_date | No | ||
| priority | No | ||
| components | No | ||
| issue_type | Yes | ||
| start_date | No | ||
| assignee_id | No | ||
| description | No | ||
| fix_versions | No | ||
| story_points | No | ||
| custom_fields | No |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||