GitHub issues, on a faster board
Mirror any repository's issues — or a GitHub Projects v2 board — into Laya and triage on a snappier, more visual surface. Dragging a card to Done really closes the issue in GitHub; dragging it back reopens it. Two-way sync, no migration.
Mirror a repository — or a Projects v2 board
One GitHub connection can mirror both kinds of board, and you pick per board which to bring in.
Repository issues
A repo's issue list becomes a board. Lanes come from each issue's open/closed state plus its status labels, and milestones show up as sprints — you can even create new milestones without leaving Laya.
GitHub Projects v2
A Projects v2 board mirrors with lanes read from its Status single-select field. Moving a card writes the Status field and closes or reopens the underlying issue. Iterations appear read-only — they stay managed in the Projects UI.
Either way, lanes map onto Laya's four sync buckets — Queued, In motion, Done and Hold — and a column-mapping drawer lets you point any label or status value at a different bucket when the defaults don't match your workflow.
What syncs — and in which direction
Edits made in Laya call the GitHub API immediately, with a per-item badge showing Queued, Syncing, Synced or Failed. When you close an issue from Laya, repo boards swap a scoped lane label while preserving every other label you've applied.
| Data | GitHub → Laya | Laya → GitHub |
|---|---|---|
| Issues | Yes — repositories & Projects v2 | Yes — create, edit, close, reopen |
| Status | Open/closed + status labels, or the Projects v2 Status field | Yes — Done closes the issue; only the lane label swaps, the rest are kept |
| Assignees | Yes | Yes — each edit replaces the full set |
| Milestones (as sprints) | Yes — repository boards | Yes — create and assign from Laya |
| Projects v2 iterations | Read-only | No — managed in the Projects UI |
| Description | Yes — Markdown to Laya blocks | Yes — blocks back to Markdown |
| Comments | Yes — read in the side panel | Yes — post from Laya |
| Pull requests | Not mirrored | — |
| Attachments | No | No |
Descriptions and comments convert between Markdown and Laya blocks. Headings, lists and paragraphs convert faithfully; tables, code fences and inline marks flatten to plain text — worth knowing if your issues are code-heavy.
Straight answers on scope and timing
The edges, stated up front — they matter more than a longer feature list.
- Pull requests are not mirrored — boards cover issues and Projects v2 items only.
- Issues imported onto a master board keep syncing title, status and description in both directions — priority, story points, due dates, assignees and milestones don't sync on those imported rows yet.
- Attachments don't sync in either direction.
- Assignee edits replace the whole set, so a simultaneous edit made in GitHub can be overwritten.
Connection playing up? See the GitHub & GitLab connection troubleshooting guide.
OAuth for speed, a fine-grained token for least privilege
Two ways in — pick the one that matches your security posture.
Continue with GitHub
One-click OAuth: approve, pick an account or organisation, choose boards. Note the OAuth repo scope covers every repository your account can access — convenient, but broad.
Fine-grained token
For tighter control, a fine-grained personal access token needs only Issues (read & write) and Metadata (read) — plus Projects (read & write) for Projects v2 boards — and can be limited to exactly the repositories you choose.
Held safely
Credentials are stored encrypted and never returned by any API response. Connecting and disconnecting need a workspace Owner or Admin, and disconnecting never touches your GitHub data.
Put GitHub issues next to the rest of the plan
A master board imports GitHub issues as native Laya issues alongside work from Jira, Azure DevOps, monday.com and GitLab — milestones and iterations can carry over as sprints, and a user-mapping step assigns items to the right teammates. See the master boards guide or compare coverage in what syncs per provider.
Free while Laya is in early access. Mirror your first repository in minutes.