jira_update_issue
Modify Jira issues by updating fields, changing statuses, linking Epics, and attaching files using a JSON-based input for precise control and automation.
Instructions
Update an existing Jira issue including changing status, adding Epic links, updating fields, etc.
Input Schema
Name | Required | Description | Default |
---|---|---|---|
additional_fields | No | Optional JSON string of additional fields to update. Use this for custom fields or more complex updates. | {} |
attachments | No | Optional JSON string or comma-separated list of file paths to attach to the issue. Example: "/path/to/file1.txt,/path/to/file2.txt" or "["/path/to/file1.txt","/path/to/file2.txt"]" | |
fields | Yes | A valid JSON object of fields to update as a string. Example: '{"summary": "New title", "description": "Updated description", "priority": {"name": "High"}, "assignee": {"name": "john.doe"}}' | |
issue_key | Yes | Jira issue key (e.g., 'PROJ-123') |
Input Schema (JSON Schema)
You must be authenticated.
Other Tools from MCP Atlassian
- confluence_attach_content
- confluence_create_page
- confluence_delete_page
- confluence_get_comments
- confluence_get_page
- confluence_get_page_ancestors
- confluence_get_page_children
- confluence_search
- confluence_update_page
- jira_add_comment
- jira_add_worklog
- jira_create_issue
- jira_delete_issue
- jira_download_attachments
- jira_get_agile_boards
- jira_get_board_issues
- jira_get_epic_issues
- jira_get_issue
- jira_get_project_issues
- jira_get_sprint_issues
- jira_get_sprints_from_board
- jira_get_transitions
- jira_get_worklog
- jira_link_to_epic
- jira_search
- jira_transition_issue
- jira_update_issue
Related Tools
- @1broseidon/mcp-jira-server
- @1broseidon/mcp-jira-server
- @George5562/Jira-MCP-Server
- @1broseidon/mcp-jira-server
- @sooperset/mcp-atlassian