How two-way sync works

Laya keeps your boards and your existing tools in step in both directions. Connect Jira, Azure DevOps, monday.com, GitHub or GitLab and Laya streams a live, editable mirror of your boards. Nothing is migrated: your tool stays the system of record, and edits made on either side flow to the other.

One connection, two layers

Every integration follows the same shape:

• Connected boards are live mirrors. Each item on the external board appears as a card backed by a durable, synced copy in Laya — kept until you disconnect — so boards open instantly and update as changes arrive. Edits you make write straight back to your tool.
• Linked items are real Laya work items created when you import from a connected source. Each keeps a link to its external counterpart, and the pair stays in sync continuously.
• Master boards mirror every attached source's items as real Laya cards, so two-way sync works there exactly as it does for any imported item. See Master boards.

Not sure whether to mirror or import? Start with Mirror vs import and Native vs Connected vs both.

When you edit in Laya

Edits push to your tool immediately, as part of the edit itself. Renaming a card, dragging it to another column or changing a due date each fires a write to the provider straight away, and the result is recorded in the connection's Sync log.

Pushes are deliberately best-effort. If your tool is unreachable or rejects the write, Laya keeps your edit locally, records the failure, and lets the next inbound sync reconcile the two sides. A failed push never rolls back what you did in Laya.

When something changes in your tool

Changes flow back into Laya in three ways: instant push over a webhook (Jira), background polling, and manual sync.

Master boards add a Sync all boards action that live-pulls every provider attached to the board in one go and reports how many items were refreshed.

How fresh should boards feel?

• Laya → your tool: immediate. The write happens during your edit. Connections made through the installed Laya Board for Jira app queue the write and apply it within seconds.
• Jira → Laya: typically well under a minute with a webhook configured, since events are processed every 15 seconds.
• Azure DevOps → Laya: around a minute, via the background poll.
• monday.com, GitHub, GitLab → Laya: around a minute where background polling is enabled; otherwise whenever you press Sync now.

What mirroring means for your data

The connect flow puts it plainly: Laya keeps the board where it lives today 'and streams a live, editable mirror — nothing is migrated.' Concretely, Laya stores:

• A durable, synced copy of each mirrored item — title, status, assignees, dates and a link back to the original — kept until you disconnect, so boards open instantly. Comments are read live from the source rather than stored, and attachments are view-only (Jira) or copied only by a one-off import.
• For imported items, a real Laya work item plus a link record that keeps it paired with the original.
• Your connection credentials, encrypted at rest with AES-256-GCM. They are never displayed again in the UI or returned by the API.

Removing a mirrored board removes Laya's synced copy only: your tool is untouched, and you can re-mirror at any time. See Disconnecting safely for the full picture.