Connecting a project to GitHub

Connect a project to a repository and every new issue, feature request and change request on it also lands as a GitHub issue. It is set up per project and takes three fields.

1. Open Organisations, click into the organisation, then into the project.
2. Switch to the GitHub tab.
3. Enter the Repository owner, for example the account or team the repository sits under.
4. Enter the Repository name.
5. Paste a Personal access token. The form asks for exactly what it needs: a fine-grained token with Issues read and write access to that repository, and it is stored encrypted.
6. Click Connect.

The token is checked against GitHub before anything is saved, so a typo or a token that cannot reach the repository fails right there rather than three days later. Once accepted it is sealed and never shown again. If you lose it, issue a new one and reconnect.

From then on the mirror runs one way, out of Certainty:

• New issues, feature requests and change requests are created as GitHub issues, titled with the record reference and carrying a link back to the record.
• Each one is labelled with its type and a priority label.
• Moving a record to closed, cancelled or rejected closes the mirrored issue. Any other status reopens it, so a reopened record never leaves a stale closed issue behind.
• Nothing done in GitHub flows back, and the mirror never blocks or slows a helpdesk write. If the integration is having a bad day, your record still saves.

When a sync does fail, the card shows a Last sync error banner with the message and how long ago it happened, so you are not guessing. Disconnect stops new mirroring, and existing linked GitHub issues keep their links.