Plan GitHub Project work. Send decisions back.
Bring issues, pull requests, and draft items from one organization-owned GitHub Project into SprintBee. Estimate together, then write accepted points to the Project fields you choose.
- ✓ Issues, pull requests, and Project drafts
- ✓ Mapped status, priority, iteration, and estimate fields
- ✓ Selected-repository access stays enforced
3Project work comes in. Team decisions go back.
Bring the work your team already tracks
Choose one organization-owned GitHub Project for the Workspace. Search and import eligible issues, pull requests, and draft items across its granted repositories, with Project and repository context attached.
Map the field once, then stop retyping points
Map SprintBee's accepted estimate to a GitHub Project number, text, or single-select field. Each accepted value writes back to the Project item whether it is backed by an issue, pull request, or draft.
Break oversized work down without losing its home
Review a split in SprintBee before anything is created. GitHub issues become repository sub-issues in the Project; pull requests and draft parents produce new Project drafts.
Built for organization-owned GitHub Projects
✓ Supported
- GitHub.com and GitHub Enterprise Cloud organizations
- Organization-owned Projects with issues, pull requests, and drafts
- All-repository or selected-repository GitHub App installations
- Mapped status, priority, iteration, and estimate fields
- Automatic refresh of imported, incomplete work items
⚠ Not supported in this release
- User-owned Projects or personal OAuth connections
- Self-hosted GitHub Enterprise Server
- Importing an issue or pull request that is not already in the selected Project
- Automatic queue insertion when new items are added to GitHub
- Editing pull-request descriptions or commenting on Project drafts
Common questions about the GitHub integration
- Who needs to connect the GitHub App?
- A SprintBee organization owner starts the connection, and a GitHub organization administrator installs or approves the SprintBee GitHub App. The SprintBee owner then reviews the verified GitHub organization before completing the pairing.
- Do I need to grant access to every repository?
- No. The GitHub App can be installed for all repositories or selected repositories. SprintBee includes Project drafts and items backed by granted repositories; items outside the repository grant are omitted without exposing their details.
- Which GitHub work items can I estimate?
- You can import Project items backed by issues or pull requests, plus Project draft items. The item must already belong to the single GitHub Project configured as the Workspace source.
- Does SprintBee automatically import every new Project item?
- No. Your team chooses what enters the SprintBee queue. Webhooks and scheduled reconciliation refresh work that has already been imported and is not complete; they never turn Project membership into automatic queue insertion.
- How does estimate write-back work?
- Choose a compatible GitHub Project number, text, or single-select field. When the moderator accepts an estimate, SprintBee writes the value to that field on the Project item and reports whether the update succeeded or needs attention.
- What happens if repository access changes or the App is removed?
- Previously imported work stays in SprintBee. An inaccessible item is marked unavailable and its GitHub actions are disabled; restoring access can make it usable again. Uninstalling the App disables the connection without deleting completed history.
For permissions, mappings, lifecycle behavior, and troubleshooting, read the GitHub integration guide.
Bring your GitHub Project into the planning room.
Start with one Workspace, connect one Project, and keep the team's accepted estimates where the work already lives.