Gmail and GitHub integrations

Connect optional integrations and understand their scope and failure handling.

Google login versus Gmail

Google sign-in verifies identity for invited access. It does not request permission to send mail. Gmail uses a separate administrator-connected shared sender with send-only authorization and per-user notification preferences.

Open the shared integration controls in Site settings as an administrator. Connect the intended sender through Google's consent flow and verify the resulting status. Do not paste integration secrets into tickets, release notes or documentation screenshots.

Notification delivery

Eligible events enter a durable delivery queue. Messages contain the source/ticket name or key, event summary and secure destination, rather than making private content public. Access is checked again before delivery. Inbox remains useful when email is disabled or unavailable.

Inspect visible failures and reconnect when authorization is revoked. Provider rate limits and configured daily attempts can delay or stop retries. Retries are bounded; a failed delivery is not evidence that the underlying ticket edit failed.

Mention destinations can point to ticket fields/comments, releases or sprint goals. Changing access after an event may prevent delivery. A Google sender connection does not grant the sender account project membership.

Connect GitHub

An administrator installs/connects the configured GitHub App for selected repositories and maps repositories to projects. Limit installation access to the repositories the workspace needs. Project members then see eligible branch, commit and pull-request activity associated with ticket keys, with manual association where offered.

Use a ticket key in the relevant development reference, for example SAMPLE-14 in a branch or pull-request title. Inspect the Development tab on the ticket. A key match links activity; it does not grant repository or project access.

Updates and limitations

Signed, deduplicated webhooks provide updates; bounded reconciliation supplements them. Reconciliation examines a bounded recent set rather than promising an unlimited historical GitHub import. Deleted branches, disconnected repositories and stale credentials can alter visible activity.

The integration is read-only: no automatic ticket transitions, two-way issue sync, branch/tag creation or deployment. Release Git references record a link to a branch/tag; marking a release live does not publish a GitHub release.

Troubleshoot safely

Check the installation/repository mapping, current access and event status before manually relinking. Reconnect through administrator controls when necessary. Do not disclose credentials while reporting a failure. Integration settings and tokens are excluded from portable content backups and must remain local to the installation.