Remove a link
unlink_issuesRemove a link.
version is the version of THIS issue (from get_issue). target is the linked issue's key as stored in frontmatter.links — of this or another project of the company; the inverse link in the other project is removed too. A delivers link to a release (KEY/R-n) cannot be removed here (the target must be an issue key): call update_issue with links = the complete list from get_issue minus that entry.
WRITE: version must be the version from your latest read of this file (get_issue for issues, list_comments for comments, list_sprints for sprints, get_doc for project docs, read_file for md files). If the file changed since, the call fails with 409 version_conflict and the error contains the current file (details.current, details.current_version): re-read it, re-apply your change on top of the current content and retry with the new version. Never overwrite someone else's change blindly — if your change and theirs disagree, ask the user which to keep.
You act with exactly the rights of the user who owns this token; a project you cannot see returns not_found.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| target | Yes | Issue key `{PROJECT}-{n}`, e.g. `KJ-101`. | |
| version | Yes | Version of the file you read. Required on every delete (spec principle 7). | |
| issue_key | Yes | Issue key `{PROJECT}-{n}`, e.g. `KJ-101`. | |
| link_type | Yes | Link types, stored on the source issue. board-core keeps the inverse on the target in step: blocks↔blocked_by, duplicates↔duplicated_by, clones↔cloned_by, relates↔relates. `delivers` (D131 (1)) points at a release (`id` = releaseRef `KEY/R-n`, same company) — the goal or deal is delivered by that release; no inverse is written (releases are not issues). | |
| project_key | Yes | Project key, e.g. `KJ`. 2–10 chars, uppercase letters and digits, starts with a letter. |