GitHub GraphQL issue updates accept issue type metadata
Introduced 2026-07-14 · score 0.91
HOW TO USE IT
When a workflow updates an issue type through `updateIssue`, set `issueType` in the `UpdateIssueInput` object. Supply the issue type ID and, optionally, confidence, rationale, or a human-review suggestion flag.
mutation UpdateIssueType($input: UpdateIssueInput!) { updateIssue(input: $input) { issue { id } } }{ "input": { "id": "<issue-node-id>", "issueType": { "issueTypeId": "<issue-type-id>", "confidence": "HIGH", "rationale": "<reason>", "suggest": false } } }WHY THIS HELPS
When maintaining a repository workflow that updates issue types through GitHub GraphQL, use the new issue type input where applicable.
REQUIREMENTS AND LIMITATIONS
- UpdateIssueInput.id (required): Node ID of the issue to modify.
- UpdateIssueInput.issueType: Issue type update object; mutually exclusive with `issueTypeId`.
- IssueTypeUpdateInput.issueTypeId: Issue type ID to set; pass null to clear the issue type.
- IssueTypeUpdateInput.confidence: Agent confidence level: `HIGH`, `MEDIUM`, or `LOW`.
- IssueTypeUpdateInput.rationale: Reason for the selected value; maximum 280 characters.
- IssueTypeUpdateInput.suggest: If true, stores the value as a pending suggestion for human review instead of applying it.
FIRST-PARTY EVIDENCE
- https://docs.github.com/en/graphql/overview/changelog#schema-changes-for-2026-07-14
- https://docs.github.com/en/graphql/reference/issues
Check the installed version and the source before using it. Entry JSON