List a work item's links
GEThttps://
Returns every link touching one work item, in both directions: the links it is the source of and the links it is the target of, which is what the linked items section in plnnrly shows.
Access
- Token scope
- api:
read: project_management Without it:
403 insufficient-token-scope. - Permission
- project_management::
view_backlog Without it:
403 insufficient-permission. - Rate cost
- 1 unit, read bucket.
view=detailmakes it 3. Adds: each include +1. - Also
If-None-Matchanswers304when nothing changed. Never cached:private, no-store. Unknown query parameters are refused, never ignored.
Both are checked, scope first. A token never does more than its user. How access is checked
direction and relationship on each row are relative to the work item in the path, so the same link reads forward / blocks here and inverse / is blocked by from the other end. The path accepts a numeric id or an issue key, so work-items/ACM-123/links works. There is no organisation-wide collection of links and no filter[source_work_item_id] or filter[target_work_item_id]: the path supplies both. Ordered by id ascending, and meta.page.total is always present; ?with_total is a 400. Listing additionally requires project_management::manage_work_items on the work item.
Path parameters
Query parameters
Unknown parameters are refused with 400, naming the parameter.
18 parameters in 5 groups
Views
Pagination
Rows per page. At most 25 when include names a to-many relation; a larger value is 400 invalid-query-parameter.
Default: 25
Filters
- =
- equals
- [in]
- any of a comma-separated list
- [null]
trueorfalse: whether it is empty- [gte][lt]
- at least, less than
- [ne]
- not equal
Creation timestamp. Pair with sort=id for a stable full export.
User who created the link. [null] selects links whose creator has since been deleted.
A comma-separated list of at most 100 values.
Relationship type: blocks, clones, duplicates, merged_into, causes, relates_to or split_to. The value is stored from the source item's point of view, so it does not flip on an inverse link: filter on blocks and you get both the items this one blocks and the items that block it.
A comma-separated list of at most 100 values.
blocksclonesduplicatesmerged_intocausesrelates_tosplit_to
New values may be added.
Sorting
| Key | Sorts by |
|---|---|
id | Id, ascending. An id never changes, so use this for a stable full export. |
updated_at | Last-write timestamp; pair with the id tiebreaker for sync. |
Prefix a key with - for descending.
Includes
| Path | Adds | Cost |
|---|---|---|
source_work_item | Work item the link points away from, with its issue key and title. | +1 |
target_work_item | Work item the link points at, with its issue key and title. | +1 |
Request headers
A correlation id of your own. It is recorded in our logs next to the server's request id but never returned: the response header always carries the server's id. A value that does not match the pattern is discarded silently, never rejected.
Response 200
Returns a page of WorkItemLinkList rows.
The rows, each a WorkItemLinkList.
per_page, next_cursor, prev_cursor, total, current_page, last_page.
self, next, prev.
Each row is a WorkItemLinkList: 12 fields.
Headers
ETag- A weak validator (
W/"…") of the rendered page. RateLimit- The IETF
httpapi-ratelimit-headersform of your remaining allowance on the tightest bucket this request touched. RateLimit-Policy- The ceiling and window of that bucket, as
<limit>;w=<seconds>. X-Request-Id- The server-generated ULID correlating this response with our logs.
Every response also carries Cache-Control, Vary, X-Content-Type-Options, X-Plnnrly-Api-Version, X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset. Headers and versioning
Work item the link points away from. On a link created through POST work-items/{work_item}/links this is always the work item named in the path.
The relationship, stored from the source item's point of view: blocks, clones, duplicates, merged_into, causes, relates_to or split_to. Only relates_to is symmetric.
blocksclonesduplicatesmerged_intocausesrelates_tosplit_to
New values may be added.
User who created the link, or null where that account has since been deleted. Resolve it with GET /api/v2/users/{user}; it is not includable.
Which way this link points relative to the work item you asked about: forward when that item is the source, inverse when it is the target. On the flat GET work-item-links/{work_item_link} there is no work item in the path, so the link is read on its own terms and this is always forward.
The relationship in words, from the point of view of the work item you asked about: blocks from the source end, is blocked by from the target end. Always in English: the API pins the locale.
Work item the link points away from.
Work item the link points at.
Errors
8 errors every operation can return: 304, 400, 401, 404, 406, 429, 500, 503
304 Not modified.
400 Bad request.
idempotency-key-requiredinvalid-cursorinvalid-query-parametermalformed-requestunsupported-parameter
401 Unauthenticated.
404 Not found.
406 Not acceptable.
429 Too many requests.
500 Server error.
503 Service unavailable.
This path allows GET, POST. Anything else answers 405.
Something wrong or missing on this page? Tell us