Integrations and sync FAQ
Quick answers about sync speed, editing in both places, multiple connections, disconnecting and who can set up integrations.
Last updated
Short answers on how two-way sync behaves day to day. For the full picture, start with How two-way sync works.
Speed and direction
How fast is sync?
Edits made in Laya are pushed to the connected tool immediately, as part of the edit itself. Inbound speed varies by provider: Jira changes typically land within about 15–45 seconds when a webhook or the Laya Board for Jira app is delivering events, Azure DevOps is polled roughly every 60 seconds, and monday.com, GitHub and GitLab update when you press Sync now unless background polling is enabled for the deployment. See How two-way sync works.
Does every field sync?
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.
What happens if I edit the same item in Laya and in the other tool?
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.
Can I make sync one-way?
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.
Connections and control
Who can set up or remove a connection?
Connecting or disconnecting a tool requires the workspace Owner or an Admin, and that capability cannot be delegated to other roles. See Managing connections.
Can I connect more than one site or organisation?
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.
What happens when I disconnect?
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.
How do I check whether sync is healthy?
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.
Email support@laya.net — include what you expected, what happened, and a link to the affected board or item so we can help quickly.