Skip to content
Integrations

Connect Jira, Azure DevOps, monday.com, GitHub and GitLab — without moving a thing

Laya mirrors the boards your teams already use onto one fast, beautiful surface. Connecting a tool streams a live, editable copy of its boards into your workspace with two-way sync: edit in Laya and it lands in the source tool, edit in the source tool and it flows back. Nothing is migrated, so there is nothing to un-migrate later.

The model

Connect once. Your whole workspace benefits.

A workspace Admin connects a tool one time. From then on, every member can open its mirrored boards, drag cards, edit fields and post comments — no per-person setup, and viewers do not need their own account in the source tool.

A live mirror, not a migration

Your work stays where it is. Laya keeps a synced copy of each mirrored item — title, status, assignees, dates and links — so boards open instantly, and removes that copy if you ever disconnect.

Two-way sync

Mirrored boards are fully editable. Moves, field edits, new items and comments write straight back to the provider, and provider-side changes flow into Laya.

One place for everything

Mirrored boards sit alongside your native Laya boards, and a master board can layer sources from several tools into a single view your whole team shares.

5
trackers with full mirroring connectors
2-way
every connected board is editable, not read-only
0
items migrated — your source tool stays in charge
Five connectors

Pick your tool

Jira and Azure DevOps connect with OAuth; GitHub and GitLab connect with OAuth or a personal access token; monday.com connects with an API token. Every connector follows the same model: authorise, choose the boards to mirror, and you are live.

Jira

Atlassian OAuth

The richest connector: sprints, backlog, epics and comments — with webhook-driven updates that land in near real time.

Explore the Jira integration →

Azure DevOps

Microsoft OAuth or PAT

Mirror every work item type in a project — states map through each process’s own categories, and iterations come along too.

Explore the Azure DevOps integration →

monday.com

API token

Mirror boards and items whether status lives in a Status column or in groups — and edit most column types from Laya.

Explore the monday.com integration →

GitHub

OAuth or fine-grained PAT

Mirror repository issues and Projects v2 boards; moving a card to Done closes the real issue, milestones act as sprints.

Explore the GitHub integration →

GitLab

OAuth or access token

Mirror project issues and issue boards — scoped labels become lanes, and self-managed instances are supported.

Explore the GitLab integration →

Honest note on freshness: every connector gets instant, push-based updates — Laya registers the webhooks itself (Jira, Azure DevOps, GitLab, monday.com, and GitHub repository boards), and the installed Laya Board for Jira app pushes events directly. A background poll keeps running underneath as the safety net, so a hook removed in your tool slows a board down rather than stopping it. The one by-design exception: a GitHub Projects board spans repositories, so it updates on the poll.

Two ways in

Mirror it — or import it

Mirroring

The source tool remains the system of record. Laya shows a live, editable projection that stays in sync both ways. This is where most teams start — there is no cutover and no retraining.

Importing

Importing copies items into Laya as native rows you own — used when composing master boards, and available as a dedicated import wizard for Jira. Imported items keep their link to the source, so they carry on syncing.

Not sure which fits? Read the honest comparison of mirroring vs importing in the Help Centre.

Governance

Who can connect, and how you keep an eye on it

Admins connect; everyone benefits. Connecting, mirroring and disconnecting require the connectors:manage capability, held by the workspace Owner and Admins. Other members can open mirrored boards, view the sync log and run Sync now — if you lack the rights, the screen says so and points you to an Admin.
Every connection is monitored. Each connection has a Manage page with a live health state (Healthy, Degraded, Needs attention or Idle), the last sync time, a Test connection button and a read-only sync log of recent inbound and outbound events — so a failing connection surfaces without a refresh.
Credentials stay sealed. Connection credentials are stored encrypted (AES-256-GCM) and are never shown again in the interface. Disconnecting removes Laya’s synced copies — it never deletes anything in your source tool.

More detail in the Help Centre: managing connections and health and disconnecting safely.

Bring your boards together — without moving them

Laya is free during early access. Connect a tool in minutes and see your work on one live surface.