# GitHub Enterprise Server (on-prem) — Issue Tracking API: gotchas

> Canonical URL: https://developers.apideck.com/apis/issue-tracking/github-server/gotchas

## POST /issue-tracking/collections/{collection_id}/tickets

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.

## PATCH /issue-tracking/collections/{collection_id}/tickets/{ticket_id}

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).


[API reference](https://developers.apideck.com/apis/issue-tracking/reference.md) · [Coverage matrix](https://developers.apideck.com/apis/issue-tracking/coverage)