Changelog

What changed—and whichplanning problem it addresses.

A dated record of meaningful product changes. Longer releases are split into scannable outcomes so you can see what became easier.

Release history

Latest updates first

This page records shipped product work. Marketing-page copy or layout changes are not added as product releases.

  • Teams keep recurring planning setup together

    Recurring refinement no longer requires rebuilding membership, access, naming, and shared AI context for every session.

    • Invite a team once, manage member roles, and add the team automatically to each new team session.
    • Choose a default access mode: open, approval, or email-only.
    • Create session-name templates with date and counter tokens.
    • Fund and control a shared AI credit pool with usage history and transfer-back.
    • Team admins can request cross-session summaries and per-member estimation insights; identities are anonymized before AI processing.

  • AI support follows the estimation problem

    Optional actions now help prepare work, build shared understanding, investigate disagreement, and carry useful patterns into the next session.

    • Enrich a story with a clearer description and acceptance criteria, or suggest a safer backlog order.
    • Explain a story in plain language and request a deck-valid estimate suggestion with rationale.
    • Summarize why estimates diverged after reveal so the team can discuss the assumptions that matter.
    • Generate retrospective narratives, session summaries, and analytics recommendations.
    • Use monthly credits, buy more, or connect an OpenAI, Anthropic, Google, or Grok key on Organizer.

  • Free sessions no longer run into an active-room cap

    Free and anonymous users can create as many active planning sessions as needed.

    • Unlimited active sessions are available to Free and anonymous organizers.

  • Notion estimates return to the backlog

    Teams can close the planning loop in Notion, while API users can automate session workflows.

    • Write finalized estimates to a Notion number or select property, a page comment, or both.
    • Use the public API to manage sessions, stories, participants, join requests, and bans.
    • Subscribe to webhooks with custom headers, URL checks, opaque ULID identifiers, and recent-delivery history.

  • Distributed estimation gains context and follow-through

    Async voting, explanation around each card, source write-back, and retrospectives make the result useful beyond one reveal.

    • Set per-story async voting windows, collect rationale and confidence, and auto-reveal after invited voters respond.
    • Write finalized estimates back to Jira story-point fields and GitHub comments, labels, or both.
    • Review consensus rate, rounds to consensus, large disagreements, and per-session retrospective patterns.
    • Use similar past stories to anchor the next estimate.
    • Load optional analytics and external widgets only after granular cookie consent.

  • Large session lists are easier to navigate

    Organizer dashboards can find the right room without scanning every session.

    • Search, filter, and sort the sessions list on the Organizer plan.

  • Backlogs enter the room without manual copying

    Organizers can import prepared work from common source tools and reuse the estimation setup.

    • Import from Notion databases, GitHub repositories, Jira projects, or CSV with flexible column mapping.
    • Sign in or link an Atlassian or Microsoft account.
    • Create and save custom estimation decks.

  • Discord becomes a planning entry point

    Teams can reach the room from the conversation they are already having.

    • Sign in or link a Discord account.
    • Start planning poker sessions with the Discord /pokor command.

  • Account access no longer requires a social login

    Passwordless email access gives teams another route into persistent sessions.

    • Sign in with a one-time email code.
    • Unlink OAuth accounts after a verified email is available.

  • Slack can start the room

    Teams can create a session from Slack instead of switching context first.

    • Start planning poker sessions with the Slack /pokor command.

  • Profiles and mobile dashboards become easier to recognize

    Identity and session navigation are clearer across devices.

    • Upload a profile avatar or use an auto-generated one.
    • Use the improved mobile dashboard layout.

  • The first complete planning room ships

    Teams can estimate together live, invite guests, choose a deck, keep history, and export the result.

    • Run real-time sessions with live updates and Fibonacci, T-shirt, Powers of 2, or custom decks.
    • Invite guests with a display name and no account.
    • Sign in with Google or GitHub for persistent access across devices.
    • Export voting history as CSV or PDF and use light or dark themes.

Cookie preferences

Essential cookies keep Pokor working. Optional analytics only load if you say yes. Privacy policy