Connect Jira

Connecting Jira mirrors your Jira projects into Laya as live, editable Connected boards. Nothing is migrated — Jira stays the system of record while changes sync both ways.

Why connect Jira

• Mirror whole Jira projects — company-managed projects bring all their boards along as sub-boards.
• Work in either place: dragging a card in Laya runs a real Jira transition, and Jira edits appear in Laya.
• Manage sprints from Laya — create, edit and move issues to sprints or the backlog.
• Read and post Jira comments live from the issue side panel, with Jira's own permissions enforced.
• Optionally import Jira issues as native Laya rows later, via the import wizard.

Before you start

There are three ways to authenticate:

• OAuth (recommended) — the Authorize with Jira button signs you in with Atlassian and grants Laya scoped access in one consent screen.
• API token — the "Advanced — connect with an API token instead" option takes a Site URL, Account email and API token.
• The installed app — sites running the Laya Board for Jira app appear as one-click connect offers, with no token at all. See Laya Board for Jira.

The OAuth consent asks for read and write access to Jira work — projects, issues, fields, statuses and users — plus Jira Software boards, sprints and epics, webhook management and offline access for token refresh. Laya deliberately does not request Jira administration scopes (manage:jira-configuration, manage:jira-project). See Provider permissions and scopes.

Connect step by step

1. Start the connect flowFrom your workspace, create a new board and choose the connect option — or open the Connected tab on the workspace home and choose Connect Jira. The flow runs Why · Source · Connect · Done.
2. Pick Jira as the sourceOn the "Which tool is it in?" screen, choose Jira.
3. AuthoriseOn "Authorize & choose boards", select Authorize with Jira and complete the Atlassian consent screen — or open the API-token disclosure and enter your Site URL, Account email and API token.
4. Choose a Jira siteIf your Atlassian account can reach more than one site, pick one on the "Choose a Jira site" screen. This step is skipped when there is only one.
5. Choose where it lives in LayaOn "How should this work in Laya?", pick Connect to my personal workspace (recommended for trying things out), Connect to existing workspace if the site already has a shared workspace, or Set up a shared workspace for my team.
6. Choose boards to mirrorPick projects from the "Choose boards to mirror" list — rows are labelled Company-managed or Team-managed, and each has a 2-way sync toggle. Use Select all, search, or Refresh to find more.
7. MirrorSelect Mirror N boards → and wait for "You're live in Laya". From there, Open board jumps straight in, or Compose a master board layers sources together.

Your mirrored projects now appear under the Connected tab, live and editable. Company-managed projects open with a picker for their individual boards (sub-boards).

Connecting while signing in

If you signed in with Atlassian and granted Jira access during sign-in, Laya asks "How should this Jira work in Laya?" with two options: Just for me (recommended — a private mirror in your own workspace, nobody else affected) or Set up a shared workspace for my team, where teammates who sign in with the same provider join automatically. A shared workspace stays "unclaimed" until a verified Jira admin claims it with the Claim workspace button. You can also choose "Skip for now — just sign me in".

What syncs

Issues imported as native Laya rows (via the import wizard or a master board) keep syncing title, status, priority, due date, assignee, description, labels, story points and issue type in both directions.

Sync triggers and timing

• Laya → Jira: immediate. Edits are pushed to Jira as part of the action itself.
• Jira → Laya: instant push via webhook. The connection's Settings tab shows a Webhook URL; add it in Jira under Admin → System → Webhooks. Laya does not register the webhook for you. Events queue safely and are processed every 15 seconds, so changes typically land within about 15–45 seconds.
• Installed-app connections push automatically — no webhook setup needed; the Laya Board for Jira app delivers events itself.
• Polling fallback. A background poll can pull recent changes when webhooks are unavailable — control it with the Polling toggle in the connection's Settings tab.
• On demand. Every mirrored board has Sync now, and opening an issue's side panel pulls its latest state from Jira instantly.

Who Jira says made the edit

On an OAuth connection, your edit is attributed to you in Jira's history if you have linked your own Jira access for the connected site (or you own the connection); otherwise it falls back to the connection owner's account. API-token connections always write as the single configured account. On installed-app connections, members with a usable linked token get a banner toggle choosing between "You" and "Laya Board" attribution.

Managing the connection

The connection's Manage page (workspace Settings → integrations → Jira) has Boards, Sync log and Settings tabs: per-board Sync now, Board Studio and Remove actions, a health card with the last sync time, a Test connection button, Refresh credentials to re-authorise, and Disconnect. If authorisation expires you'll see "Jira authorization expired — reconnect required." — reconnecting fixes it. See Managing connections.

Limitations

• One Jira site per workspace.
• Attachments are view-only on mirrored boards — no uploads to Jira from Laya. (The import wizard does copy attachments into Laya.)
• The webhook must be added manually in Jira admin — except on installed-app connections, which push automatically.
• API-token connections attribute every outbound edit to the one configured account.