AnchorView

Shape

• issueAnchorIssueSummary or nulloptionalThe work item's number, type, title and status. Absent briefly after the work item is deleted, until its anchors are removed.

  • The AnchorIssueSummary schema
  • iidIssueId (integer · int64)
  • scope_idstringThe id of the group or repository the work item lives in.
  • scope_typeScopeTypegrouprepositoryWhether the work item lives in a group or a repository. With scope_id and iid it is the item's current address — which need not be the repository the anchor is in: an item that moves keeps its anchors where the code is.
  • 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)
  • titleIssueTitle (string)
  • uidIssueUid (string · uuid)
  • 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.

Graph

Used by