SprintPoker for Jira

SprintPoker for Jira is SprintPoker’s app for Jira: planning poker inside Jira. SprintPoker for Jira and Laya.net work as one app. This guide covers SprintPoker for Jira’s side: connecting a Jira site to Laya.net, guests, what a Jira admin controls, and disconnecting. To play a session from Laya.net, see Play one session with SprintPoker for Jira.

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.
• SprintPoker 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 SprintPoker 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.

1. Start the connectionIn SprintPoker for Jira, choose Connect Laya.net in the Dashboard’s header. A Jira admin can also start from Connect to Laya.net in the Laya.net connection section of SprintPoker’s settings (Apps, Manage your apps). The SprintPoker page, Share and Create Session offer it too. 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.
2. Approve on Laya.netChoose Approve in Laya.net. Laya.net opens in a new tab, on the Connect SprintPoker for Jira to Laya.net page, 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 SprintPoker for Jira 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.
3. 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. 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.
4. 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 SprintPoker 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 Dashboard’s header shows Laya.net connected.

Where session data is kept

• No issue data is sent to connect.
• SprintPoker displays issue details, such as descriptions and comments, live from Jira and never stores them with a session.
• SprintPoker for Jira 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.

More in SprintPoker privacy and data.

What a Jira admin controls

Jira admins manage the connection in SprintPoker’s settings (Apps, Manage your apps), 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 SprintPoker (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).

Everyone else sees the connection on the Dashboard and the SprintPoker page, where SprintPoker for Jira says “Only Jira admins can disconnect it or change its settings.”

Guests

Each session has one Laya.net link, for everyone. In SprintPoker for Jira, Share (beside the session’s name) 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.

• 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 creating 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.
• External links sent before still work: they open the session’s Laya.net link.
• 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.

What guests see

• Each issue’s key and title.
• Its description, where a Jira admin’s What guests may see is Key, title and description and the host shares descriptions. It is read live from Jira when a guest looks, and never kept.
• The description shows as it does in Jira: its formatting, its links and its pictures, where Laya.net can read them for guests (through this app, in its latest version). A mention shows the person’s name only.
• Its comments, and its assignee and reporter, only on a site connected to Laya.net, where a Jira admin allows them and the host shares them.
• Never the issue’s attachments outside its description, its “Open in Jira” link or email addresses. Guests never save to Jira.

More in Join a session and invite guests.

Disconnect

Only a Jira admin can disconnect a site, with Disconnect in the Laya.net connection section. SprintPoker for Jira asks first, in Disconnect SprintPoker 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.

Troubleshooting