Skip to content
Jira integration

Mirror Jira boards into Laya — with two-way sync

Point Laya at a Jira project and get a like-for-like board on a faster surface: every column, card, sprint and field where it belongs. Edits made in Laya are pushed to Jira immediately; changes in Jira flow back in near real time. Jira stays the system of record — nothing is migrated.

Atlassian OAuthTwo-way syncWebhook push — near real timeNo migration
Connecting

One authorisation, then pick what to mirror

Connecting Jira is a single OAuth consent with Atlassian — no app to install in Jira and no tokens to paste. You can even sign in to Laya with Atlassian and flow straight into connecting.

1 · Authorise with Atlassian

Grant Laya read/write access to Jira in one consent screen. Prefer not to use OAuth? An API token connection (site URL, account email and token) is available as an advanced alternative.

2 · Choose your site & projects

Pick the Jira site to bind (skipped when you only have one), then choose the projects to mirror. Company-managed projects bring all of their Agile boards along as sub-boards; team-managed projects mirror directly.

3 · You’re live

Laya streams each project onto a live, editable board with two-way sync per board. From there you can open boards straight away or compose a master board across sources.

Already using the Laya Board for Jira app inside Jira? Sites connected through the installed app appear as one-click connect offers — no tokens involved at all.

Private or shared

Your own mirror, or one workspace for the whole team

Just for me

Mirror your Jira into a private workspace. Nobody else is affected — no team setup and no admin sign-off needed. Ideal for trying Laya against real work.

A shared workspace for the team

Each Jira site gets one canonical shared workspace. Teammates who sign in with Atlassian and reach the same site join automatically as contributors — no invites to chase.

Admin claim, verified against Jira. A shared workspace starts unclaimed. When a verified Jira site admin arrives — Laya checks the ADMINISTER permission with Jira itself — they can claim ownership of the workspace, and the previous owner becomes a maintainer. Governance ends up where it belongs, without blocking the first person through the door.

Weighing up private vs shared? See the guide to choosing your Jira setup.

Field coverage

What syncs — the richest connector Laya has

Mirrored Jira cards carry far more than a title. Laya projects each issue with:

Status & status categorySprintsAssignee & reporterPriorityDue dateIssue typeLabelsParent / subtask nestingEpic linkWorklogsCustom fieldsFix versionsComponents

Laya → Jira

Title, status transitions, priority, due date, assignee, issue type, story points, rich-text descriptions and labels all push to Jira the moment you edit. On an OAuth connection, edits are attributed to you in Jira’s history when your own Atlassian identity reaches the site.

Jira → Laya

Title, status (via the board’s own column mapping), priority, due date, assignee, labels, description, story points and issue type flow back — fanning out to every Laya board the issue is linked on, master boards included.

Comments are read live, not copied. The issue panel lists, adds, edits and deletes Jira comments through Jira’s own API, with Jira’s own permission model enforced — so what you see is always the real thread, never a stale copy. Attachments are viewable in Laya but new uploads still happen in Jira.

Full field tables for every provider: what syncs, per provider.

Freshness

Webhook-driven updates, in near real time

Jira is currently the only Laya connector with push-based inbound sync. Add Laya’s webhook URL in Jira (Jira Admin → System → Webhooks) and changes made in Jira typically land in Laya within about 15–45 seconds — no polling delay, no manual refreshing. Install the Laya Board for Jira app and events push automatically, with no webhook setup at all.

Instant push

Jira events queue into a sync inbox that Laya drains every 15 seconds, deduplicated and re-fetched from Jira before applying — trust, but verify.

Self-healing on open

Opening an issue’s side panel live-pulls it from Jira and reconciles the card on the spot — so the detail view is always current, whatever the trigger.

Visible health

A per-connection sync log records every inbound and outbound event, boards carry per-card sync badges, and a Test connection button verifies the link in one click.

The mechanics in depth: how two-way sync works and sync health, logs and recovery.

Beyond fields

The full Jira toolkit, on a faster surface

Connected Jira boards are not a thin viewer. From Laya you can plan and manage sprints (create, edit, move issues to a sprint or back to the backlog), work a proper Backlog tab, apply the board’s quick filters, use saved views, log work, watch issues, manage fix versions and components, edit custom fields, browse the change history and run bulk operations — and create or delete real Jira issues without leaving Laya.

Want native copies instead? Jira also has a dedicated five-step import wizard that copies issues into Laya as native rows — descriptions, comments, attachments, sprints, epics and parent/subtask links included — with an explicit user-mapping step. Imported rows keep their Jira link, so they carry on syncing.
The fine print

Honest limitations

One Jira site per workspace. A workspace binds to a single Jira site by design — it keeps the site-to-workspace model unambiguous. Working across several sites means one workspace per site.
The webhook is set up by you. Laya shows you the webhook URL, but does not register it in Jira automatically — adding it takes a minute in Jira Admin. Skip that step and sync still works; it is simply not instant. The installed app needs no webhook setup.
Attachments are view-only. Jira attachments render in Laya through a read-only proxy; uploading new files to Jira from Laya is not supported. The import wizard does copy attachments into Laya for imported rows.
Governance

Held safely, admin-controlled, easy to leave

Held safely

Connection credentials — OAuth tokens and API tokens alike — are stored encrypted at rest and never returned by any API response or shown in the interface again.

Admin-controlled

Connecting, mirroring and disconnecting need a workspace Owner or Admin. Other members can open mirrored boards and run Sync now — if you lack the rights, the screen says so and points you to an Admin.

Clean disconnect

Disconnecting stops the sync and removes Laya’s mirrored boards and their cached issues. Your native Laya boards are kept — and your Jira data is never touched.

See your Jira projects on a faster board

Free during early access. Connect with Atlassian, choose your projects, and you are live in minutes — with Jira untouched.

Prefer to stay inside Jira? Laya Board for Jira brings Laya boards into your Jira instance.