jira_create_issue

Create Jira issues with optional Epic links or parent for subtasks. Define project, type, summary, assignee, and custom fields to streamline task management and tracking.

Instructions

Create a new Jira issue with optional Epic link or parent for subtasks

Input Schema

Name	Required	Description	Default
`additional_fields`	No	Optional JSON string of additional fields to set. Examples: - Set priority: {"priority": {"name": "High"}} - Add labels: {"labels": ["frontend", "urgent"]} - Add components: {"components": [{"name": "UI"}]} - Link to parent (for any issue type): {"parent": "PROJ-123"} - Custom fields: {"customfield_10010": "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', 'Epic', 'Subtask'). The available types depend on your project configuration. For subtasks, use 'Subtask' (not 'Sub-task') and include parent in additional_fields.
`project_key`	Yes	The JIRA project key (e.g. 'PROJ', 'DEV', 'SUPPORT'). This is the prefix of issue keys in your project. Never assume what it might be, always ask the user.
`summary`	Yes	Summary/title of the issue

Input Schema (JSON Schema)

{
  "properties": {
    "additional_fields": {
      "default": "{}",
      "description": "Optional JSON string of additional fields to set. Examples:\n- Set priority: {\"priority\": {\"name\": \"High\"}}\n- Add labels: {\"labels\": [\"frontend\", \"urgent\"]}\n- Add components: {\"components\": [{\"name\": \"UI\"}]}\n- Link to parent (for any issue type): {\"parent\": \"PROJ-123\"}\n- Custom fields: {\"customfield_10010\": \"value\"}",
      "type": "string"
    },
    "assignee": {
      "description": "Assignee of the ticket (accountID, full name or e-mail)",
      "type": "string"
    },
    "description": {
      "default": "",
      "description": "Issue description",
      "type": "string"
    },
    "issue_type": {
      "description": "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.",
      "type": "string"
    },
    "project_key": {
      "description": "The JIRA project key (e.g. 'PROJ', 'DEV', 'SUPPORT'). This is the prefix of issue keys in your project. Never assume what it might be, always ask the user.",
      "type": "string"
    },
    "summary": {
      "description": "Summary/title of the issue",
      "type": "string"
    }
  },
  "required": [
    "project_key",
    "summary",
    "issue_type"
  ],
  "type": "object"
}

MCP Atlassian

jira_create_issue

Instructions

Input Schema

Input Schema (JSON Schema)

Other Tools from MCP Atlassian

Related Tools