link_issues

A tool of the Sprintree MCP server. All MCP docs · Back to the tool list

added 2026-10-03

Link two issues of the same project (needs edit access). kind "blocks": `from` blocks `to` (to cannot be finished before from); "blocked_by": `from` is blocked by `to` (the same link written from the other end); "relates": the two are related (symmetric). An issue cannot be linked to itself, the same link cannot be added twice, an issue has at most 200 links, and both issues must be in one project. A `blocks` link that closes a cycle (A blocks B blocks A) is created anyway and the result warns about it. Both issues get a history entry, and their followers a notification. get_issue_details lists the links of an issue, with the ids unlink_issues takes.

  • fromstringrequired
    Issue key, e.g. ITR-12
  • kindenumrequired
    blocks (from blocks to), blocked_by (from is blocked by to) or relates (symmetric)
    blocksblocked_byrelates
  • tostringrequired
    The other issue's key, in the same project

Returns

  • cyclebooleanrequired
    true when a blocks link closed a cycle (the link exists anyway)
  • fromstringrequired
  • kindstringrequired
    blocks, blocked_by or relates, as seen from from
  • link_idstringrequired
    Id of the new link (unlink_issues takes it)
  • tostringrequired
  • warningstringoptional
    What the cycle is, when there is one
  • 2026-10-04 — Claude Code 2.1.288+ (clientInfo claude-code): the text of a successful answer is itself up to 512 bytes, else "Result in structuredContent (N bytes)."; structuredContent and errors are unchanged. See /docs/mcp.