Skip to content
GitmoapAPIBeta
Schema

IssueRelationView

A relation, with the work item at the other end summarised. A relation whose other end you cannot see is left out entirely, so its existence is not disclosed.

Shape

  • created_atstring
  • kindRelationKindblocksblocked_byrelates_toduplicatesHow two work items relate. A relation is always visible from both ends: blocks on one item reads as blocked_by on the other, while relates_to and duplicates read the same from either side.
  • status_categoryStatusCategorytriagetodoin_progressin_reviewblockeddonecancelledThe fixed category behind a status. A status also has a name, which the team owns and may rename freely; the category is the part the platform reasons about. A team can call a status "Ready for QA" and the platform still knows it is in_review — so a board can place it in a column, a merge can move it, and a progress rollup can count it as not done.
  • status_idStatusId (string)
  • targetIssueRef
  • titleIssueTitle (string)
  • work_item_typeWorkItemTypeepicstorybugtaskspikechoreincidentsub_taskThe kind of work item. The type decides where an item may live (a group or a repository), which types it may have as children, and which fields it accepts.

Example

Synthesized example
{
"created_at": "2026-10-08T12:42:32Z",
"kind": "blocks",
"status_category": "triage",
"status_id": "7fb712d4-5500-497f-9b47-3b2d1a5d529d",
"target": {
"iid": 33,
"scope": {
"group": "4c1d8e2f-6a3b-4f90-b7c5-1e2d3c4b5a69"
}
},
"title": "Label every synthesized example",
"work_item_type": "epic"
}

Graph

Used inside

No schema contains this one.

Contains

Used by

Sent by 0 operations

No operation takes it as a request body.

Returned by 4 operations