Play with Laya.net
Connect your Jira site to Laya.net so people can join Planning Poker Agility sessions from either app, and invite guests.
Last updated
On this page
Planning Poker Agility and Laya.net work as one app. Once someone connects your Jira site to Laya.net, new sessions on the site also show on Laya.net, and people can join from either app.
What it is
- Everyone can keep estimating in Jira.
- Once a Jira site is connected to Laya.net, new sessions on that site also show on Laya.net, so people can join from either app. Everyone sees the same issue, the same votes and the same results.
- On Laya.net, a session created in Planning Poker Agility opens at the table too, until its host or a moderator chooses Classic there. In a window narrower than 768 pixels, such as a phone, Laya.net shows its Classic room.
- Planning Poker Agility displays issue details, such as descriptions and comments, live from Jira and never stores them with a session.
- Guests don’t need a connection. A host can let guests join a session with its Laya.net link and just a name, on any site where a Jira admin allows them (see Guests).
Who can connect a site
By default, everyone who uses Planning Poker Agility on the Jira site can connect it to Laya.net. They don’t need to be a Jira admin. A Jira admin can narrow it to Jira admins only, or to Members of these groups (see What a Jira admin controls). Jira admins can always connect.
To approve the connection on Laya.net, you need a Laya.net account and a team workspace where you can connect tools (the Add connections & mirror boards permission, which Members have by default). Your own Atlassian account must be able to open the Jira site.
Connect a Jira site to Laya.net
Connecting 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.
- Start the connectionIn Planning Poker Agility, choose Connect Laya.net at the top of Your tables. A Jira admin can also start from Connect to Laya.net in the Laya.net connection card of the app’s Get started page (in Jira settings, under Apps). The Connect to Laya.net dialog says what connecting does. Choose Connect to Laya.net: the dialog shows a pairing code and how long it has left.
- Approve on Laya.netChoose Approve in Laya.net. After Jira asks you to confirm, Laya.net opens in a new tab with your code filled in. Sign in first if you need to. The page names the Jira site and shows the code: check it is the one Planning Poker Agility shows. A code works once, for 15 minutes. If your own Atlassian account isn’t linked to Laya.net yet, the page offers Continue with Atlassian first, then brings you back. If your Laya.net account has two-factor authentication, that step shows the field for your code straight away: enter it, then press Confirm and connect.
- Choose a workspaceUnder Connect it to this team workspace, choose the workspace and press Approve. Jira sites connect to team workspaces, never to a personal one. One Jira site goes with one Laya.net workspace, so when the site already has one, the page offers only that one, whichever app connected it. If no Laya.net workspace has the site’s Jira connected yet, approving connects it to this workspace too (its boards and issues). The page says how, and Atlassian may ask you to allow it first. More about this page.
- Finish in JiraBack in Jira, the dialog updates on its own and shows Connected to your workspace, with “People can now play this site’s Planning Poker Agility sessions from Laya.net too.” Choose Continue. If the code ran out before you approved it, the dialog says This code expired: choose Get a new code and approve the new one.
From then on, new sessions on the site show in both apps, and the top of Your tables shows Laya.net connected.
Sites that also use SprintPoker for Jira
- A Jira site has one Laya.net workspace, so Planning Poker Agility connects to the workspace the site already uses, whichever app connected it.
- Each app keeps its own sessions, lists and monthly counts, even on the same site.
- A new session created on Laya.net on one of the site’s boards shows in one Jira app: in SprintPoker for Jira when it is connected, otherwise in Planning Poker Agility.
Where session data is kept
- No issue data is sent to connect.
- Planning Poker Agility displays issue details, such as descriptions and comments, live from Jira and never stores them with a session.
- Planning Poker Agility keeps its own record of each session. A session that also shows on Laya.net is kept there too: what it runs on, such as its name, who joined, the votes and results, and each issue’s key and title. If AI hints are on, the hints are kept with the session.
- Laya.net keeps shared sessions in the United States, whatever data residency your Jira site uses, and keeps them after the session ends. Planning Poker Agility’s own data is held in Europe (Sweden and the UK).
- Whenever someone uses the app, our servers ask Laya.net whether the site is connected, with the site’s ID and that person’s Atlassian account ID. For a site that was never connected and never had a session open to guests, Laya.net keeps nothing from the check. When someone connects the site, our servers also send that person’s name, so Laya.net can show who connected it.
- Whether or not the site is connected, Laya.net also keeps daily counts of each site’s sessions, numbers with the site’s ID that name no one, which it reads from our servers.
What each service keeps, and where, is on the trust page.
AI in shared sessions
In a session shared with Laya.net, AI hints and writing help come from Laya.net instead, which uses Anthropic. Laya.net makes one hint per issue, once, and both apps show it. A Jira admin’s Enable AI, on the app’s settings page (in Jira settings: Apps, then Planning Poker Agility), covers them too: turning it off while the site is connected also turns Laya.net’s AI off in the sessions shared with it, and if the site is connected after that, choose Apply to Laya.net there.
Limits in shared sessions
Sessions started in Planning Poker Agility keep the free plan’s limits in both apps: up to 8 people per session (guests count) and 30 issues per session, and up to 20 new sessions per person each month. Sessions started on Laya.net have no limits for now, in both apps, and don’t count towards the 20.
| What | Started in Planning Poker Agility | Started on Laya.net |
|---|---|---|
| People in a session | Up to 8, counting guests | No limits for now |
| Moderators in a session | 1 | No limits for now |
| Issues in a session | Up to 30 | No limits for now |
| New sessions | 20 each month for each person | No limits for now, and not counted |
| Decks | Preset decks only; card values can’t be edited | No limits for now |
| Automatic AI hints | Not included; a moderator can ask for an AI hint at any time | No limits for now |
Guests
Each session has one Laya.net link, for everyone. In Planning Poker Agility, Share shows it as the Laya.net link, with Copy and Open. Members of the session’s Laya.net workspace open it with their own accounts.
While the session’s Guest access is on, guests join with the same link with just a name, after a human check. If the session’s Ask before letting people in is on, or the session is private, they wait in the lobby until a moderator lets them in. For a session created in Planning Poker Agility, turning on guest access also turns on Ask before letting people in, unless it was set before.
- A new session starts with Guest access off, in both apps, unless a Laya.net workspace admin chose otherwise. The host turns it on when setting up the session, or later in Share.
- Turning Guest access off, in Share, removes the guests in the room straight away and stops new guests joining. Revealed votes and results are kept.
- A site needs no Laya.net connection for guests. For a whole site, only a Jira admin turns guests off, with Allow external guests in the Laya.net connection section of the app’s settings page.
- In a session started in Planning Poker Agility, guests count towards the 8 people it holds.
What guests see
- Each issue’s key and title.
- On a site connected to Laya.net, also its description, its comments, and its assignee and reporter, where a Jira admin allows them (What guests may see) and the host shares them. They are read live from Jira when a guest looks, and never kept.
- On a site that is not connected, also its description, where a Jira admin allows it (What guests may see) and the host shares it: Laya.net reads it live from Jira through the app when a guest looks, and never keeps it. Its comments, assignee and reporter need a connected site.
- Never the issue’s attachments outside its description, its “Open in Jira” link or email addresses. Guests never save to Jira.
What a Jira admin controls
Jira admins manage the connection on the app’s settings page (in Jira settings: Apps, then Planning Poker Agility), in the Laya.net connection section. It shows the status, the Laya.net workspace, and when and by whom the site was connected. There a Jira admin can:
- choose Who can connect this site to Laya.net: Everyone who uses Planning Poker Agility (default), Jira admins only, or Members of these groups, picked from the site’s Jira groups. Jira admins can always connect, and changing this never disconnects the site;
- Disconnect the site (see Disconnect);
- choose what guests may do on the site, with Allow external guests and What guests may see (see Guests).
The app’s Get started page shows Start Your Estimation Session, with your boards, the estimation modes and a Laya.net connection card. That card offers Connect to Laya.net while the site is not connected. Once it is, the card offers Open Laya.net and, to Jira admins, Settings, which opens the settings page. Get started has no settings and no Disconnect.
Everyone else sees the connection at the top of Your tables, where Planning Poker Agility says “Only Jira admins can disconnect it or change its settings.”
Disconnect
Only a Jira admin can disconnect a site, with Disconnect in the Laya.net connection section of the app’s settings page. Planning Poker Agility asks first, in Disconnect Planning Poker Agility from Laya.net? Then:
- Sessions stay, and nothing is deleted: votes, results, saved estimates and history stay.
- Sessions created in Jira pause. They stay listed and are read-only in both apps, and open rounds wait with their votes hidden. They carry on when a Jira admin connects the site again.
- Sessions created on Laya.net leave the Jira list and continue on Laya.net.
- New sessions on the site stay in Jira only. People can no longer find the site’s sessions on Laya.net or join them with a Laya.net account.
- Guests aren’t affected. Every session keeps its guest access and guest choices, and new sessions can still be opened to guests. Only a Jira admin’s Allow external guests turns guests off for the site. Guests of a paused session see it paused and read-only, and no new guest joins it while it is paused.
After a Jira admin disconnects the site, only a Jira admin can connect it again. If Planning Poker Agility is uninstalled, its shared sessions stay readable on Laya.net, and nothing is deleted.
Troubleshooting
| What you see | What to do |
|---|---|
| In Planning Poker Agility: “A Jira admin limited who can connect this site to Laya.net.” followed by who can | A Jira admin chose who may connect. Ask a Jira admin, or someone the message names, to connect the site. |
| In Planning Poker Agility: “A Jira admin turned off the Laya.net connection for this site. Only a Jira admin can turn it back on.” | A Jira admin disconnected the site. Ask a Jira admin to connect it again. |
| In Planning Poker Agility: This code expired. On Laya.net: “This code has expired: codes last 15 minutes.” | A code works once, for 15 minutes. In Planning Poker Agility, choose Get a new code, then approve the new code. |
| On Laya.net: the Jira site “is already connected to the Laya.net workspace” named on the page | One Jira site goes with one Laya.net workspace, whichever app connected it. A member of that workspace who can connect tools approves the code there. |
| On Laya.net: “You don’t have a team workspace where you can connect tools yet.” | Jira sites connect to team workspaces. Choose Create a team workspace: it opens in a new tab, and the page updates when you come back. |
| On the session’s Laya.net link: “This session isn’t open to guests.” | Guests join only while the session is running and its Guest access is on, and while a Jira admin allows external guests. Where a Jira admin doesn’t, Share in Planning Poker Agility says “A Jira admin doesn’t allow external guests on this site.” |
Email support@laya.net and include what you expected, what happened, and a link to the affected board or item so we can help quickly.