How to link Jira issues (issuelinks) with atlassian-mcp-server MCP tools?
I'm using atlassian-mcp-server to manage Jira tickets and can't create issue links (issuelinks). createJiraIssue ignores issuelinks passed in additional_fields, and editJiraIssue returns "Field does not support update 'issuelinks'" when issuelinks is placed in the fields payload. Is there a supported way to link Jira issues with these MCP tools?
Originally asked on GitHub: https://github.com/atlassian/atlassian-mcp-server/issues/45
3 answers
Resolved: the Atlassian maintainers confirmed issue-linking support was implemented; the issue was closed as completed in March 2026. The thread does not state the exact tool name or version that shipped it.
The root cause is how the Jira Cloud API handles issuelinks. Links are modified through the
updateobject (with verbs likeadd/remove) in the PUT payload, or through the dedicatedPOST /rest/api/3/issueLinkendpoint — not through thefieldsobject. TheeditJiraIssuetool wraps thefieldspayload, so puttingissuelinksthere produces the error "Field does not support update 'issuelinks'".One reported workaround attempt: injecting
update.issueLinksinto the MCP payload. The server accepted the payload but silently performed no linking, so that path was not usable before the fix.What to do now: update atlassian-mcp-server to its latest release and check its documented tool list or changelog for the new linking capability. The original request asked for either an
update-object payload ineditJiraIssueor a dedicated tool (e.g.,linkJiraIssues) wrapping the issueLink endpoint; the maintainers confirmed the work was done, but the thread does not specify which form it took. (Verifying against the current release's tool list is general advice, since the thread gives no version details.)Did this work for you?What a GitHub user tried on GitHub (Didn't work)
Passed issuelinks in additional_fields to createJiraIssue and in the fields parameter of editJiraIssue; the edit attempt failed with "Field does not support update 'issuelinks'" because the tool wraps fields rather than the Jira update object.
Source: https://github.com/atlassian/atlassian-mcp-server/issues/45 (opens external site)
Did this work for you?What @danielmklein tried on GitHub (Didn't work)
Injected an update.issueLinks object into the MCP payload; the server accepted it but did not actually perform any issue linking.
Did this work for you?
Related questions
- Atlassian MCP server broken after Claude Code dropped SSE: what works?
- Atlassian MCP server in Claude Code/Cursor: "We are having trouble completing this action" error
- Atlassian MCP server drops connection after 15-20 min with 401 Unauthorized
- atlassian-mcp-server: Can I authenticate with an API token instead of OAuth?
- Restrict atlassian-mcp-server to certain Jira projects / Confluence spaces?