Create Issue
jira_create_issueCreate a Jira issue in a specified project with summary, description, issue type, and optional assignee, components, or additional fields. Link to an epic or set parent for subtasks.
Instructions
Create a new Jira issue with optional Epic link or parent for subtasks.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| summary | Yes | Summary/title of the issue | |
| assignee | No | (Optional) Assignee's user identifier (string): Email, display name, or account ID (e.g., 'user@example.com', 'John Doe', 'accountid:...') | |
| components | No | (Optional) Comma-separated list of component names to assign (e.g., 'Frontend,API') | |
| issue_type | Yes | Issue type (e.g. 'Task', 'Bug', 'Story', 'Epic', 'Subtask'). The available types depend on your project configuration. For subtasks, use 'Subtask' (not 'Sub-task') and include parent in additional_fields. | |
| description | No | Issue description in Markdown format. On Jira Cloud, use '{expand:Title}...{expand}' for a collapsible section. | |
| project_key | Yes | The JIRA project key (e.g. 'PROJ', 'DEV', 'ACV2'). This is the prefix of issue keys in your project. Never assume what it might be, always ask the user. | |
| additional_fields | No | (Optional) JSON string of additional fields to set. Examples: - Set priority: {"priority": {"name": "High"}} - Add labels: {"labels": ["frontend", "urgent"]} - Link to parent (for any issue type): {"parent": "PROJ-123"} - Link to epic: {"epicKey": "EPIC-123"} or {"epic_link": "EPIC-123"} - Set Fix Version/s: {"fixVersions": [{"id": "10020"}]} - Custom fields: {"customfield_10010": "value"} |
Output Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |