Skip to content
GitmoapAPIBeta
Schema

IssueTransitionSkippedMetadata

The details of an automatic status change that the workflow's transition rules forbade.

Shape

  • fromStatusCategorytriagetodoin_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.
  • reasonstring
  • sourceTransitionSourcemanualbranch_createdmerge_request_openedmerge_request_mergedmerge_request_closedclosing_keywordquick_actionscorecard_checkcommit_orphanedpipeline_evidenceWhy a work item's status changed: whether a person decided it, a commit or merge request said so, or a pipeline's evidence proved it.
  • toStatusCategorytriagetodoin_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.

Example

Synthesized example
{
"from": "triage",
"reason": "reason-36dd",
"source": "manual",
"to": "triage"
}

Graph

Used inside

No schema contains this one.

Contains

No named schema inside.

Used by

Sent by 0 operations

No operation takes it as a request body.

Returned by 0 operations

No operation returns it directly.