Before you start
What would you like to improve?
Other (new hosted tool / product capability)
What problem does this solve?
The server can create Jira issue links but has no way to remove one. createIssueLink was added in #45, but there is no matching delete/remove tool, and no other tool exposes it: editJiraIssue rejects issuelinks updates (the original complaint in #45), and there is no deleteIssueLink / removeIssueLink.
Concrete case: an agent creates a "Relates" link, then the correct relationship turns out to be a parent/epic link (set via editJiraIssue fields.parent). The now-redundant "Relates" link cannot be cleaned up through the MCP server at all — it has to be deleted by hand in the Jira UI. Any workflow that creates a link and later needs to correct or undo it is stuck, so agents are effectively one-way on issue links.
What would you like to see?
A dedicated tool to delete an existing issue link, wrapping the Jira Cloud REST API v3 Delete issue link operation — DELETE /rest/api/3/issueLink/{linkId} — e.g. deleteJiraIssueLink(cloudId, linkId).
API reference: Jira Cloud platform REST API v3 — Issue links, specifically the Delete issue link endpoint (DELETE /rest/api/3/issueLink/{linkId}). Requires issue linking to be enabled on the site.
The link id is already discoverable today: getJiraIssue with fields: ["issuelinks"] returns each link's id, so a delete-by-id tool composes cleanly with what already exists. This closes the create/read/delete loop for issue links (create via #45, read via getJiraIssue/issuelinks, delete via the new tool).
Anything you've already tried or considered?
Anything else?
Noting the template's guidance that hosted-server capabilities are best raised via Atlassian Support / Community — filing here because this is the direct follow-up to #45, which was accepted and delivered in this repo. Happy to also raise it through Support if that's the preferred channel.
If this issue is accepted, we're happy to raise a PR implementing the tool.
Filed by an AI assistant (Claude) on behalf of @fgm .
Before you start
What would you like to improve?
Other (new hosted tool / product capability)
What problem does this solve?
The server can create Jira issue links but has no way to remove one.
createIssueLinkwas added in #45, but there is no matching delete/remove tool, and no other tool exposes it:editJiraIssuerejectsissuelinksupdates (the original complaint in #45), and there is nodeleteIssueLink/removeIssueLink.Concrete case: an agent creates a "Relates" link, then the correct relationship turns out to be a parent/epic link (set via
editJiraIssuefields.parent). The now-redundant "Relates" link cannot be cleaned up through the MCP server at all — it has to be deleted by hand in the Jira UI. Any workflow that creates a link and later needs to correct or undo it is stuck, so agents are effectively one-way on issue links.What would you like to see?
A dedicated tool to delete an existing issue link, wrapping the Jira Cloud REST API v3 Delete issue link operation —
DELETE /rest/api/3/issueLink/{linkId}— e.g.deleteJiraIssueLink(cloudId, linkId).API reference: Jira Cloud platform REST API v3 — Issue links, specifically the Delete issue link endpoint (
DELETE /rest/api/3/issueLink/{linkId}). Requires issue linking to be enabled on the site.The link id is already discoverable today:
getJiraIssuewithfields: ["issuelinks"]returns each link'sid, so a delete-by-id tool composes cleanly with what already exists. This closes the create/read/delete loop for issue links (create via #45, read viagetJiraIssue/issuelinks, delete via the new tool).Anything you've already tried or considered?
editJiraIssuewith anissuelinksupdate payload — not supported (same limitation reported in Feature Request: Support for linking Jira issues (issuelinks) via MCP tools #45 for the add direction).createIssueLink,getIssueLinkTypes, andgetJiraIssueRemoteIssueLinks— none can remove a standard issue link.Anything else?
Noting the template's guidance that hosted-server capabilities are best raised via Atlassian Support / Community — filing here because this is the direct follow-up to #45, which was accepted and delivered in this repo. Happy to also raise it through Support if that's the preferred channel.
If this issue is accepted, we're happy to raise a PR implementing the tool.
Filed by an AI assistant (Claude) on behalf of @fgm .