Add a link from this issue to another
link_issuesAdd a link from this issue to another.
Board-core also writes the inverse link on the target issue (blocks ↔ blocked_by, duplicates ↔ duplicated_by, clones ↔ cloned_by, relates ↔ relates) — in the target's own project when it is another one. id (spec D131) is an issue key of THIS project or of another project of the SAME company (KJ-120): you must be able to open both projects, else 403 link_target_forbidden (details.project_key) — do not retry, tell the user who can. Cross-company links do not exist. type: delivers (goals, deals) takes a release instead: id = KEY/R-n (list_releases of that project gives R-n), the release must exist (404 release_not_found) and no inverse is written — the goal or deal is delivered by that release; delivers with an issue key, or any other type with KEY/R-n, is a 400. Afterwards get_issue shows the target live in linked[] (title, status or release state and progress) and rollup fields (computed) follow.
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 |
|---|---|---|---|
| id | Yes | An issue key of this project or of another project of the company (D131 (1); you must open both, else 403 link_target_forbidden), or `KEY/R-n` with type `delivers`. | |
| 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). | |
| version | Yes | Optimistic-lock version of the file; +1 on every write. Every write must send the version it read. | |
| issue_key | Yes | Issue key `{PROJECT}-{n}`, e.g. `KJ-101`. | |
| project_key | Yes | Project key, e.g. `KJ`. 2–10 chars, uppercase letters and digits, starts with a letter. |