GitHub

SprintBee connects to organization-owned Projects on GitHub.com and GitHub Enterprise Cloud. GitHub Enterprise Server is not supported.

Connect the GitHub App#

An owner starts from Dashboard → Integrations → Add connection → GitHub and chooses the SprintBee organization that will own the connection. A GitHub organization administrator installs the SprintBee GitHub App. The SprintBee owner then reviews the organization GitHub verified and approves the pairing.

One GitHub App installation belongs to exactly one SprintBee organization. Installation access tokens are short-lived and generated only when SprintBee calls GitHub; SprintBee does not store them.

The app requests organization Projects read/write and Issue Types read, plus repository Metadata read and Issues and Pull requests write. An administrator may grant all repositories or selected repositories. Project drafts and items from granted repositories are available. Items from repositories outside the grant are omitted without revealing their details.

Configure a Workspace source#

Choose exactly one GitHub Project in the Workspace integration settings. A Project can contain work from several repositories, but the Project—not a repository—is the source boundary.

Before activation, select the Project's single-select status field and explicitly map its options to SprintBee's To do, In progress, Review, Blocked, and Done categories. Priority, iteration, and estimate fields are optional mappings. SprintBee suggests mappings but does not silently confirm them.

Supported work items#

Project issues, pull requests, and draft issues can be imported. Issue and pull-request labels, assignees, author, native Issue Type, and mapped Project fields are preserved when available. Drafts have no fabricated key; SprintBee identifies every item by its stable Project Item ID.

Issue and draft descriptions can be edited from SprintBee. Pull-request descriptions are read-only. Comments on issues and pull requests are posted by the SprintBee App and include the SprintBee participant's display name in a footer. Drafts must first be converted to issues in GitHub before they can receive comments.

Updates and unavailable items#

GitHub webhooks refresh imported incomplete items, with scheduled reconciliation repairing missed deliveries. New Project items are never imported automatically. Completed SprintBee history is immutable.

If an item is archived, deleted, removed from the Project, or becomes inaccessible because repository access changed, it remains in the SprintBee queue marked unavailable. Restoring access makes it usable again. Suspending the app marks the connection as needing reconnection; uninstalling disables it without deleting imported history.

Splitting work#

Splitting a GitHub issue creates real sub-issues in the same repository and adds them to the configured Project. Splitting a pull request or draft creates Project draft issues; that relationship is recorded in SprintBee because GitHub has no equivalent provider relationship for those parents.