Connect laya.net: external boards and master boards

Linking is optional and adds to what you have; the Jira board keeps working the same way. Linking uses a short pairing code that you approve on laya.net. You never type a password into Jira, and no issue data is sent to connect.

Link the site

1. Start the connectionOn the board, choose Connect Laya.net. The Connect to Laya.net wizard shows a pairing code and how long it has left.
2. Approve on laya.netChoose Approve in Laya.net and enter the code on laya.net. A code works for 15 minutes.
3. Choose a workspacePick the workspace to link and approve access. The app can then read and write boards in that workspace; you can revoke this at any time from the workspace settings.
4. Finish in JiraThe wizard shows that you are connected. Choose Continue.

The Laya Board for Jira user guide has every screen and message in the pairing flow.

What linking adds

• External boards: boards from Azure DevOps, monday.com, GitHub and GitLab, inside Jira and editable both ways. A field a tool cannot take back is shown read-only, with a notice.
• Master boards: one board layered from up to 50 source boards, with swimlanes per source. See master boards.
• Native Laya boards: boards that live in your laya.net workspace and need no Jira permissions.
• Mission Control gains the organisation Roadmap and Open Laya workspace ↗.
• Two-way sync between Jira and the workspace. See how two-way sync works.

Whose name is on the change

Changes made on laya.net and written back to Jira show in Jira's history as the Laya Board app by default. Members who link their own Jira access on laya.net can choose to have their edits shown as their own. See people and assignee matching.