Skip to content
Integrations · GitLab

GitLab issues and boards, in sync with Laya

Mirror project issues from gitlab.com — or your own self-managed instance — onto a faster, more visual board. Laya speaks GitLab's language: scoped labels, issue boards, milestones, weight and issue links all round-trip with two-way sync.

gitlab.com & self-managedOAuth or access tokenTwo-way sync
Made for GitLab

Your labels run the board — Laya respects that

GitLab workflows live in scoped labels like workflow::doing. Laya doesn't flatten them; it builds on them.

Pin an issue board

Pin one of a project's GitLab issue boards and its label lists become Laya's columns — or keep the whole project as one board. Switch the pinned board any time and the columns rebuild.

Surgical label writes

Moving a card swaps only the lane label and closes or reopens the issue. Every other label you've applied stays exactly as it was.

Links, weight & milestones

Manage Related, Blocks and Blocked-by links from the side panel, edit weight as story points, and track milestones as sprints — creatable from Laya on every GitLab tier.

Two-way sync

What syncs — and in which direction

Edits made in Laya call the GitLab API immediately, with a per-item badge showing Queued, Syncing, Synced or Failed so nothing disappears silently.

What syncs between GitLab and Laya, in each direction
DataGitLab → LayaLaya → GitLab
IssuesYes — per projectYes — create, edit, close, reopen
StatusOpen/closed + scoped labels, or a pinned issue board’s listsYes — close/reopen plus a targeted lane-label swap; other labels kept
AssigneesYesYes — full set; multiple assignees need GitLab Premium
Due datesYesYes
Weight (story points)YesYes
Milestones (as sprints)YesYes — creatable on every GitLab tier
Iterations (Premium)Read-onlyNo — cannot be created from Laya
Issue links (Related / Blocks / Blocked by)YesYes — link and unlink
Epics (Premium/Ultimate)Carried read-only on master-board import
DescriptionYes — Markdown to Laya blocksYes — blocks back to Markdown
Comments (notes)Yes — read in the side panelYes — post from Laya
Merge requestsNot mirrored
AttachmentsNoNo

A word on tiers: iterations, epics, weight and multiple assignees are GitLab Premium/Ultimate features, and they degrade silently on Free — a multi-assignee edit, for example, keeps only the first assignee. Full coverage detail is in the connect GitLab guide.

Connecting

gitlab.com or your own instance

Self-managed GitLab is a first-class citizen, not an afterthought — the same mirror, pointed at your instance URL.

Continue with GitLab

OAuth is the recommended path: approve the api and read_user scopes, pick a group, choose the projects to mirror. Done.

Personal access token

Prefer a token — or running self-managed? Create one with the api scope and add your instance URL. Laya validates the token against your instance before saving anything.

Guard-railed & encrypted

Instance URLs must be reachable over public HTTPS — internal and loopback addresses are rejected outright — and credentials are stored encrypted, never exposed by any API response. Connecting needs a workspace Owner or Admin.

No surprises

How fresh is the mirror — and what doesn't sync yet

The honest edges, before you connect.

Instant
Laya → GitLab. Edits push as part of the action, and open boards update live for everyone viewing them in Laya.
Sync now
GitLab → Laya. Changes arrive when you press Sync now — one click on the board or from the connection's Boards tab — and whenever you edit through Laya. Instant webhook push isn't live yet.
  • Merge requests are not mirrored — boards cover issues only.
  • Issues imported onto a master board keep pushing title, status, due date, weight and description out to GitLab — priority, assignee and issue type don't push on those imported rows yet.
  • Attachments don't sync in either direction.
  • Markdown conversion flattens tables, code fences and inline marks to plain text.

Connection playing up? See the GitHub & GitLab connection troubleshooting guide.

Beyond the mirror

One board for GitLab and everything around it

A master board imports GitLab issues as native Laya issues alongside work from Jira, Azure DevOps, GitHub and monday.com — milestones and iterations can carry over as sprints, epics carry into native epics, and a user-mapping step assigns items to the right teammates. Read the master boards guide or compare coverage in what syncs per provider.

Free while Laya is in early access. Mirror your first project in minutes.