Parameters
1 query
Query parameters
· 1issueKeystringRequiredIssue key (e.g. "PROJ-123") whose neighbours to list.
PROJ-123Returns the issues linked to the given anchor issue via pm__issue_related. Links are stored symmetrically (both directions written on each linkRelatedIssues call), so a single-direction query surfaces every neighbour. Filtered to the callers organisation on BOTH sides (anchor + target) as a defence-in-depth check on top of the write-time same-org invariant. Ordered by link creation time (newest first) and then by internal issue id for stability. The primary today writer is the inbound-mail closed-fork pipeline (reason="mail_closed_issue"`); the admin sidebar renders the list only when non-empty.
1 query
issueKeystringRequiredIssue key (e.g. "PROJ-123") whose neighbours to list.
PROJ-1231 status code documented
itemsobject[]RequiredexternalIdstringRequiredPublic 16-char identifier of the related issue.
issueKeystringRequiredHuman-readable issue key (e.g. "PROJ-123").
subjectstringRequiredIssue subject/title.
prioritynumber | nullRequiredPriority (1..5); null when unclassified.
statusobjectRequiredidnumberRequiredStatus ID.
labelstringRequiredStatus display label (localized to the viewing organisation).
categoryIdnumberRequiredStatus category ID (1=new, 2=progress, 3=waiting, 4=done).
categoryCodestringRequiredStatus category code.
reasonstring | nullRequiredOrigin of the link. Known values: mail_closed_issue (inbound-mail pipeline forked a fresh ticket because the matched issue was already closed). null for manual links written without a reason.
insertedDatestringRequiredWhen the link was created (UTC timestamp).
itemCountnumberRequiredNumber of returned rows (equals items.length).
{
"items": [
{
"externalId": "example_externalId",
"issueKey": "example_issueKey",
"subject": "example_subject",
"status": {
"id": 0,
"label": "example_label",
"categoryId": 0,
"categoryCode": "example_categoryCode"
},
"insertedDate": "example_insertedDate"
}
],
"itemCount": 0
}GET /bff/issue/related
curl -X GET "https://api.bizkithub.com/bff/issue/related?issueKey=PROJ-123" \
-H "Content-Type: application/json" \
-H "Authorization: Bearer YOUR_API_KEY"All BizKitHub public API endpoints require authentication via API key.