MCP Atlassian
by sooperset
jira_create_issue
Create a new Jira issue with optional Epic link
Input Schema
Name | Required | Description | Default |
---|---|---|---|
additional_fields | No | Optional JSON string of additional fields to set. Examples: - Link to Epic: {"parent": {"key": "PROJ-123"}} - For linking to an Epic after creation, prefer using the jira_link_to_epic tool instead - Set priority: {"priority": {"name": "High"}} or {"priority": null} for no priority (common values: High, Medium, Low, None) - Add labels: {"labels": ["label1", "label2"]} - Set due date: {"duedate": "2023-12-31"} - Custom fields: {"customfield_10XXX": "value"} | {} |
assignee | No | Assignee of the ticket (accountID, full name or e-mail) | |
description | No | Issue description | |
issue_type | Yes | Issue type (e.g. 'Task', 'Bug', 'Story') | |
project_key | Yes | The JIRA project key (e.g. 'PROJ'). Never assume what it might be, always ask the user. | |
summary | Yes | Summary/title of the issue |
Input Schema (JSON Schema)
This server cannot be installed
Other Tools
- confluence_search
- confluence_get_page
- confluence_get_comments
- confluence_create_page
- confluence_update_page
- jira_get_issue
- jira_search
- jira_get_project_issues
- jira_create_issue
- jira_update_issue
- jira_delete_issue
- jira_add_comment
- jira_add_worklog
- jira_get_worklog
- jira_link_to_epic
- jira_get_epic_issues
- jira_get_transitions
- jira_transition_issue