Skip to content

SprintPoker

Estimate together in Laya: sessions, guests, async rounds, Ready or Not and playing with SprintPoker for Jira.

  1. Get started with SprintPokerWhat SprintPoker on Laya.net is, where to find it, and how to start a session with typed-in items, cards from a Laya board or Jira issues.
  2. Run an estimation roundVote, reveal, re-estimate and save: how a live Poker session runs, and where Save & Next writes the final estimate.
  3. Async sessionsEstimate at your own pace: how an Async Poker session runs, from voting and comments to the review and Save & Next.
  4. Join a session and invite guestsThe session’s Laya.net link, guests who join with just a name, the lobby, and joining with a Laya.net account.
  5. Play one session with SprintPoker for JiraOnce SprintPoker for Jira is connected, a new session of Jira issues is in both apps, so people in Jira and on Laya.net vote in the same round: the set-up, who joins from where, and linking your Atlassian account.
  6. Ready or Not: check what is ready to estimateScan a Laya board or a Jira project before a session: an AI clarity grade and your Definition of Ready for every issue, and help to fix the gaps.
  7. Quick estimate on a cardEstimate one card from its panel without starting a session, on a Laya board or a connected Jira board: vote, reveal, and set the card’s estimate.
  8. Edit issue fields in the roomChange an issue from the room’s details panel without leaving the session: its title, its description and its fields, for Laya cards, Jira issues and typed-in items, and whose permissions apply.
  9. SprintPoker settings and display preferencesThe Connections, Workspace and Personal tabs of SprintPoker settings, and the display preferences that only you see.
  10. SprintPoker privacy and dataWhat deleting a session does, how to erase one, what guests see, what is kept for sessions shared with SprintPoker for Jira, and what happens when an account goes.
  11. Troubleshooting SprintPokerFix the common SprintPoker problems: linking an Atlassian account, Jira permission refusals, an expired Jira sign-in, estimates that didn’t save, and SprintPoker switched off.