Bring GitHub Issues into Plane through Project Sync
Connect GitHub to Plane, map a repository to a Plane project, then add the plane label to selected GitHub issues. This is ongoing integration sync rather than an isolated CSV import.
Workspace administrators configure project issue sync. GitHub integration is a Pro feature; self-hosted instances must first configure a GitHub App. Repository access and account mapping must be ready.
Example: sync three selected checkout bugs from the mobile repository into the Mobile project before deciding whether both tools should remain editable.
Step-by-step guide
Connect the GitHub installation
Open Workspace settings > Integrations > GitHub and connect the organization. Grant the Plane App only the required repositories; on self-hosted Plane complete its GitHub App setup first.
Create the project mapping
In Project Issue Sync, click + and select the Plane project and repository. Map GitHub Open and Closed to the intended Plane states.
Choose the ownership direction
Select unidirectional GitHub-to-Plane or bidirectional sync, then Start Sync. GitHub data overwrites corresponding Plane content in unidirectional mode, so agree which tool owns the record.
Sync and inspect selected issues
Add the plane label to a representative GitHub issue. Confirm its Plane work item and reciprocal links, then inspect state, description and assignee before labeling more issues.
Common mistakes
Treating synchronization as a one-time copy
Future changes continue following the mapping and direction. Do not edit Plane content expecting it to override GitHub in unidirectional mode.
Sources and verification
Based on product documentation checked on 2026-11-04. This is a documentation-based guide, not a hands-on benchmark. Features and availability can change.