Issue Tracking API

Collections

Users

Tickets

Comments

connection

GitHub Enterprise Cloud (data residency)

The date and time when the object was created.

Created at (timestamp)

When custom mappings are configured on the resource, the result is included here.

Description

name

Type

The date and time when the object was last updated.

Updated at (timestamp)

high

Completed at (timestamp)

Created by

The ticket's description. HTML version of description is mapped if supported by the third-party platform

Due date (timestamp)

The pass_through property allows passing service-specific, custom data or structured modifications in request body when creating or updating resources.

Priority

The current status of the ticket. Possible values include: open, in_progress, closed, or - in cases where there is no clear mapping - the original value passed through.

Subject

Name

Photo URL

critical

Body

GitHub always creates issues with status `open`; the `status` field is ignored on creation (you cannot create a closed or in-progress ticket). Change it afterward with an update — and note GitHub only supports `open`/`closed`. For workflow states like "in progress" or "up next", use labels via the `tags` field, or GitHub Projects.


GitHub issues only support the statuses `open` and `closed`. Any other `status` value (e.g. `in_progress`) is silently ignored and the issue's state is left unchanged. To represent workflow states like "in progress" or "up next", use labels via the `tags` field, or GitHub Projects (which are not exposed through this connector).


GitHub Enterprise Cloud (data residency)

Details