Integrations and sync FAQ

Edits made in Laya are pushed to the connected tool immediately, as part of the edit itself. Inbound is instant too: Laya registers its own webhooks with every tool (and the installed Laya Board for Jira app pushes events directly), so changes made in Jira, Azure DevOps, GitLab or monday.com land on your board within a second or two of arriving — applied the moment they're received, not queued for a sync cycle. GitHub repository boards are instant the same way; a GitHub Projects board spans repositories, so it updates on the regular poll instead. The poll keeps running underneath for everyone as a safety net, and Sync now pulls on demand. See How two-way sync works.

No — field coverage varies by provider and by direction. Jira has the richest coverage (including assignee and labels); monday.com currently syncs the least. What syncs per provider has the full tables.

Laya uses a last-writer-wins policy: the most recent edit wins, and an incoming change is skipped when your Laya edit is newer. Per-provider echo guards stop the two sides bouncing the same change back and forth. See Conflicts, loops and safety.

There is no one-way mode — connected boards are two-way by design. You can pause instead: Board settings → Integrations pauses sync per provider for a whole board, keeping the links so it resumes where it left off, and Jira-linked items also offer a per-item Pause sync.

Connecting or disconnecting a tool requires the workspace Owner or an Admin, and that capability cannot be delegated to other roles. See Managing connections.

Yes for Azure DevOps, monday.com, GitHub and GitLab — a workspace can hold several connections per provider. Jira is the exception: one Jira site per workspace, by design — to mirror a second Jira site, use another workspace. See Managing connections.

Laya deletes its mirror of the disconnected boards and wipes the stored credentials. Native boards and imported items survive as ordinary Laya items — they are simply no longer linked. Read Disconnecting safely first: disconnecting a shared team connection stops sync for everyone in the workspace.

Each connection's Manage page shows a health state — Healthy, Degraded, Needs attention or Idle (provider connection lists may label the same underlying states Broken or Disabled) — plus a per-operation Sync log; Jira connections also have a Test connection button. See Sync health, logs and recovery.