Planning Poker Agility is moving to Atlassian Forge
What the move to Atlassian Forge means for you: the timeline, the free plan, what changes, and what Jira admins need to do.
Last updated
On this page
- In one minute
- Why this is happening
- Timeline
- Do I need to do anything?
- The free plan
- What stays the same
- What’s new
- What works differently
- Your data and history
- What doesn’t come across
- For Jira admins
- Update by hand
- What you’ll see in Atlassian Administration
- Permissions and network addresses
- Installs that need help
- People without a Jira licence
- Sites with SprintPoker Free
- What users notice
- Trust badges
- Frequently asked questions
- Progress updates
- Support
- Optional and separate: SprintPoker
Planning Poker Agility is moving to Atlassian Forge. This page explains what changes, what stays the same, what (if anything) you need to do, and where to get help. We update it as the move progresses.
In one minute
- Planning Poker Agility is moving to Atlassian Forge, Atlassian’s app platform, before Atlassian ends support for the platform it runs on today, on 31 January 2027.
- It stays free, with the same name and the same Marketplace listing.
- After the update it has new limits, the same as SprintPoker Free, our other free planning poker app: up to 8 people and 30 issues per session, 20 new sessions each month, the six standard decks, 5 Ready or Not scans per person each month, and the 3 most recent sessions in the session list (older ones stay listed but can't be opened).
- Some things work differently, and a lot is new. Both are listed below.
- Each site is updated by hand: once Atlassian approves the new version, a site or organisation admin updates it in Atlassian Administration. Until then, a banner in the app counts down the days.
- Jira admins: update your site before 31 January 2027.
- The last section of this page describes a separate paid app. You never need it to keep using Planning Poker Agility within the free plan.
Why this is happening
Atlassian is ending support for Connect, the platform Planning Poker Agility runs on today. In Atlassian’s words: “Connect end of support begins on 31 January 2027.” After that date Atlassian fixes only critical security issues, and some changes may stop Connect apps working without notice. Moving to Atlassian Forge keeps Planning Poker Agility supported and lets us keep improving it.
Timeline
| Step | When | What you do |
|---|---|---|
| Announced | 21 October 2026 | Nothing yet |
| New version sent to Atlassian for review | We aim for November 2026 | Nothing yet |
| Atlassian’s review | Often two to three weeks, sometimes longer | Nothing yet |
| New version available | From approval day (the progress updates give the date) | A site or organisation admin updates the app by hand in Atlassian Administration (see Update by hand) |
| Connect end of support | 31 January 2027 | Update before this date: the app counts down the days |
Only 31 January 2027 is set by Atlassian. We change the other dates here as they become firm.
Do I need to do anything?
Jira admins. Yes, once. When Atlassian has approved the new version, a site or organisation admin updates Planning Poker Agility by hand in Atlassian Administration (see Update by hand), at a time that suits your team, for example outside meeting hours. Please do it before 31 January 2027: a banner in the app counts down the days, and shows the steps once the update is available. Before Atlassian approves the new version there’s nothing to update, and we’ll say here when there is. If your install is licensed through a Marketplace access token, contact support and we’ll help. A suspended install can’t be updated at all, even by hand, until its licence is active again (Atlassian’s rule).
Everyone else. Nothing, except to ask your Jira admin to update when the banner in the app says so. When your site is updated, reload when the app asks you to.
The free plan
After the update, Planning Poker Agility has new limits, the same as SprintPoker Free, our other free planning poker app. The previous version had no caps on sessions, people or history, so some teams will meet these limits for the first time.
| What | Free plan |
|---|---|
| People in a session | Up to 8, counting everyone: moderator, participants and observers |
| Moderators in a session | 1 (as today) |
| Issues in a session | Up to 30 |
| New sessions | 20 each month, counted over the sessions created this month in the list you can see, so on a busy site the team as a whole can reach 20 |
| Decks | The six standard decks; card values can’t be edited |
| Opening sessions from the list | The 3 most recent; older ones stay listed but can’t be opened |
| Ready or Not | 5 scans per person each month; checking a single issue from the issue view is free and not counted |
| Selecting all backlog issues at once | Not included |
| Changing a session’s issues after it starts | Not included |
| Automatic AI hints | Not included; a moderator can ask for an AI hint at any time |
The six standard decks: 0, 1, 2, 3, 5, 8, 13, 21, 34, 55, 89, ?; 1, 2, 3, 5, 8, 13, 21, 34, 55, 89; 1 to 10; 1, 2, 4, 8, 16, 24, 32, 40; 0.5, 1, 2, 3, 5, 8, 13; XS, S, M, L, XL, XXL. The room always adds a ? card for “Not sure”.
- When you reach a limit, the app tells you there and then. Nothing is deleted.
- If your team needs more than the free plan, see Optional and separate: SprintPoker at the end of this page.
What stays the same
- The name, Planning Poker Agility, and its Marketplace listing and reviews.
- The price: free.
- Estimating with cards inside Jira: pick a card, reveal together, and save the agreed estimate to Jira as yourself.
- Story points, original estimate and other number fields.
- Reference issues that update live for everyone.
- Estimates already saved in Jira: nothing about them changes.
What’s new
- Async sessions: everyone estimates in their own time before a due date, with a comment per issue.
- An AI hint when a moderator asks for one.
- Matching Issues: done issues that were estimated with the value you’re pointing at.
- A confidence check after each reveal, and richer results: average, mode, median, range and more.
- Quick estimates from the Planning Poker Agility panel in an issue.
- Edit issues during a session: field edits and status changes show up for everyone.
- A summary with Copy results when a session ends, and finished sessions can be reopened.
- Moderators can manage roles and people during a session, and anyone can look at another issue and come back.
- Ready or Not can start a session with the issues it checked already picked.
- Keyboard-friendly cards and a warning when the connection drops.
- Jira admins can delete sessions.
What works differently
Planning Poker Agility now runs on the same code as SprintPoker Free, so some things work the way they do there.
| Before (previous version) | After (new version) | |
|---|---|---|
| Usage | No caps | The free plan above |
| Decks | Standard Fibonacci (1 to 21), Time estimates, or your own values | One of the six standard decks |
| Creating a session | Three steps, then the session starts | Choose the type and settings, pick the issues on a draft, then Start Session |
| All from backlog | Yes | Not part of the free plan |
| Adding issues after the start | Yes | Not part of the free plan: pick the issues before you start |
| Sub-tasks | “Enable Subtasks” | Sub-tasks and epics aren’t offered in the issue picker |
| Votes before the reveal | Observers saw them; moderators could Peek | The room shows nobody’s vote until the reveal |
| Changing a card after the reveal | Allowed | Live sessions: Re-estimate starts a new round. Async sessions can allow updates |
| Saving | Save, or Save and vote next | Save & Next |
| Auto-reveal | Always on | A session option, on by default; when everyone online has voted, the moderator is asked whether to reveal |
| Timers | Two preset buttons | One timer: presets from 10 seconds to 5 minutes, or any number of seconds |
| Ranking and sprint moves | Drag in the room | On the Select issues page |
| Looking at another issue | Everyone followed the moderator | Anyone can open another issue and come back to vote |
| Reference issues | 3 per board | Up to 4 per project, shared by its boards |
| Definition of Ready | Per board | Per project |
| Ready or Not | 10 scans per site each month | 5 scans per person each month |
| Boards with estimation turned off | Worked, with a warning | Turn estimation on first |
| Time estimates | Converted by Jira with your site’s working hours | 8-hour days and 5-day weeks |
| Editing issues | Jira’s issue dialog for the moderator; comments for everyone | Inline edits under each person’s own Jira permissions, or Jira’s dialog; field edits and status changes refresh for everyone |
| Who can open it | Anyone signed in, including people without a Jira licence | People with a Jira licence |
| Finished sessions | Couldn’t be reopened | Can be reopened |
| Deleting sessions | The creator or the moderator | The moderator or a Jira admin |
| History | Every session | The 3 most recent can be opened from the list; older ones stay listed but can’t be opened |
| Usage report | Yes | No |
| Links that leave Jira | Opened directly | Jira asks you to confirm first |
| Choices saved in your browser | Kept | Reset once, at the update |
Your data and history
We are preparing to bring your earlier sessions across to the new version, and we’ll list exactly what comes across here once we have rehearsed the move. Final estimates are already saved in Jira, so nothing in Jira changes, and nothing is deleted.
What doesn’t come across
- Monthly scan counts: everyone starts with 5 scans.
- Choices saved only in your browser, such as filters.
- Votes in a round that is still open at the moment your site updates. Estimates already saved to Jira are safe.
- The usage report, which isn’t part of the new version.
Where it’s stored. The new version stores sessions with Amazon Web Services and MongoDB Atlas in the EU (Stockholm, Sweden). Issue details, such as descriptions and comments, are shown live from Jira and never stored with a session.
AI. The AI hint and Ready or Not send issue text to our AI provider, OpenAI, to make a suggestion, only when someone uses them. OpenAI processes these requests in the United States. Nothing changes in Jira unless someone accepts a suggestion. Whoever creates a session can turn AI hints off for it.
Who processes it. Atlassian (Forge), Amazon Web Services, MongoDB Atlas and OpenAI. Before the new version is available, we’ll list them on this page and in the Privacy & Security tab of the app’s Marketplace listing.
Personal data. The app stores Atlassian account IDs, and the names and profile picture addresses Jira shows for them, with the sessions people join.
Shared sessions. The new version contains an optional Laya.net connection, which is switched off. Nothing goes to Laya.net unless it is switched on and someone on your site chooses to use it.
Contact support with any question about your data.
For Jira admins
You update it. Once Atlassian approves the new version, a site or organisation admin updates each site by hand in Atlassian Administration, before 31 January 2027. A banner in the app counts down the days, and shows the steps once the update is available. Anyone with the old version open is asked to reload, so choose a time outside meeting hours. If your site already has the new version, its Get started page says “Planning Poker Agility is up to date”, and there’s nothing more to do.
Update by hand
Organisation admins and site admins can do this once the new version is available:
- Go to Atlassian Administration (admin.atlassian.com) and choose your organisation.
- Open Connected apps and select Planning Poker Agility.
- Choose View app details, then Update.
- If Atlassian shows “Review the updated capabilities”, check the list and confirm.
- The new version is usually ready within a few minutes. Anyone with the old version open is asked to reload.
If you’re a Jira admin without these roles, ask an organisation or site admin.
What you’ll see in Atlassian Administration
Until the new version is listed, Atlassian Administration shows: “This app is running on a platform that will be unsupported after January 2027. For migration plans or other available options, contact the vendor directly through the app’s Marketplace listing.” Once it’s listed, a site not yet updated shows: “This app version is running on a platform that will be unsupported soon. Update your app now, as the latest version could provide better support options or a migration path.” After the update, the warning goes. Jira’s app audit log lists the update as “a new installation”: that’s expected for this move, and app access rules that cover the app keep applying.
Permissions and network addresses
Before the new version is available, we’ll list here, in plain words, what it can do in your Jira and why, and the addresses it needs if your network allows only listed addresses.
Installs that need help
If your install is licensed through a Marketplace access token, contact support and we’ll help. A suspended install can’t be updated at all, even by hand, until its licence is active again (Atlassian’s rule).
People without a Jira licence
Atlassian Forge shows app pages only to people with a Jira licence who are signed in.
Sites with SprintPoker Free
Each app keeps its own sessions, lists and monthly counts, even on the same site.
What users notice
- Before the update: a banner on the session list that counts down the days to 31 January 2027 and asks your Jira admin to update. It can be made one line, and it never shows in a session.
- A short reload when your site switches over. If you’re in a session at that moment, reload when asked; estimates already saved to Jira are safe, and you may need to vote again on the current issue.
- A welcome card the first time you open the new version, with a short tour.
- A new look in Jira’s own style.
- Sessions start as drafts, and some things work differently (see above).
- The free plan’s limits, shown in the app when you reach one.
- Links that leave Jira, for example to the Marketplace, ask you to confirm before they open.
- At a limit, the app may show “Upgrade to Pro”. It opens the Marketplace listing of a separate paid app, described in the last section of this page; you never need it to keep using Planning Poker Agility within the free plan.
Trust badges
Atlassian is retiring its Cloud Fortified programme for all apps on 31 December 2026, so the badge will leave our listing too. This is not related to the move to Atlassian Forge.
Frequently asked questions
Why are there limits now?
Planning Poker Agility now runs on the same code as SprintPoker Free, our other free planning poker app, and we chose to give it the same limits. Sharing one code base means both apps get the same fixes and new features. We know this is a change for teams that used it without caps. The limits are listed under “The free plan”. If your team needs more, the last section of this page describes an optional paid app.
What happens to our earlier sessions?
We are preparing to bring them across to the new version, and we’ll say here exactly what comes across once we have rehearsed the move. Final estimates were already saved in Jira, so nothing there changes, and nothing is deleted.
Do we have to pay for anything?
No. Planning Poker Agility stays free, and the update is free. At a limit, the app may show “Upgrade to Pro”: that opens the listing of a separate paid app, described at the end of this page. You never need it to keep using Planning Poker Agility within the free plan.
Do we need to do anything?
Yes, once: when Atlassian has approved the new version, a site or organisation admin updates the app by hand in Atlassian Administration, before 31 January 2027 (see Update by hand). Everyone else only needs to ask their Jira admin when the banner in the app says so. If your install is licensed through a Marketplace access token, contact support; a suspended install can’t be updated until its licence is active again.
When will our site be updated?
When a site or organisation admin on your site updates it. The new version can be installed from the day Atlassian approves it (the progress updates below give the date); before then there’s nothing to update to. Please update before 31 January 2027.
What happens to a session that’s running when our site updates?
The old version asks everyone to reload. Estimates already saved to Jira are safe. Votes not yet revealed in the round that was open are lost, so you may need to vote again on that issue. To avoid this, a site or organisation admin can update outside meeting hours.
Can we go back to the old version?
No. Atlassian no longer supports going back from Forge to the old version. If something doesn’t work as it should, contact support and we’ll look into it.
Can we stay on the old version?
Your site keeps the old version until an admin updates it, but please don’t wait. After 31 January 2027 Atlassian no longer supports it, and it may stop working without notice.
Why can’t some people open the app after the update?
Atlassian Forge shows app pages only to people with a Jira licence who are signed in.
I don’t see an Update button.
Check three things: the new version may not be listed yet (see the progress updates); in Atlassian Administration the Update button shows to organisation and site admins, so if you’re a Jira admin without that role, ask one of them; and your site may already have the new version (its Get started page says “Planning Poker Agility is up to date”). If none of these explains it, contact support.
Why can’t we peek at votes or change a card after the reveal any more?
The new version works the way SprintPoker Free does: the room shows nobody’s vote until the reveal, and a live round’s reveal is final. To vote again, the moderator uses Re-estimate. In async sessions, the moderator can let people update their estimates.
What happened to our own card values and the time deck?
The free plan offers the six standard decks. Your own values aren’t part of it. The closest to the old Standard Fibonacci deck is 1, 2, 3, 5, 8, 13, 21, 34, 55, 89. None of the six decks has time values such as 30m or 1d, so the old Time estimates deck isn’t part of the free plan either; you can still save estimates to Original estimate (see “What works differently”).
Our site also has SprintPoker Free. Do the two apps share sessions or limits?
No. Each app has its own sessions, lists and monthly counts, even on the same site.
Will Atlassian or Agile Pulse email us about this?
Not from us: we have no email list for this app. Atlassian notifies people who watch the app on the Marketplace when it approves the new version, but other admins may not get an email. That’s why we post updates in the app and on this page.
Is our data moving?
Yes. The new version stores sessions with Amazon Web Services and MongoDB Atlas in the EU (Stockholm, Sweden). See Your data and history.
Progress updates
We post every step here, newest first: at least once a week until 31 January 2027, then whenever something changes, and promptly if anything goes wrong.
| Date | Update |
|---|---|
| 21 October 2026 | We announced the move in the app and published this page. |
Support
- Contact support: laya.net/help/contact
- In the app: Help & Support on the dashboard.
Please include your site address (for example northwind.atlassian.net) and, if you have it, the support code from the Get started page. A support code helps us find your site; it isn’t a password, and we never ask for passwords.
Optional and separate: SprintPoker
SprintPoker is our paid planning poker app for Jira. It’s a separate app, not a paid version of Planning Poker Agility, and it doesn’t have the free plan’s limits: any number of people and new sessions, up to 1,000 issues per session, full history, several moderators per session, your own card values, selecting all backlog issues at once, changing a session’s issues after it starts, automatic AI hints and unlimited Ready or Not scans.
- You never need it to keep using Planning Poker Agility within the free plan, and the free update never requires it.
- It keeps its own sessions. Your Planning Poker Agility sessions and history stay in Planning Poker Agility and don’t move to SprintPoker.
- Installing it doesn’t change the limits inside Planning Poker Agility.
- Prices are on its Marketplace listing.
What does “Upgrade to Pro” mean in Planning Poker Agility?
When you reach a free plan limit, Planning Poker Agility may show “Upgrade to Pro”. It opens SprintPoker’s listing; “Pro” is what SprintPoker calls its paid app. You can ignore it and keep using Planning Poker Agility within the free plan.
If we buy SprintPoker, do our sessions move?
No. SprintPoker is a different app with its own sessions. Your Planning Poker Agility sessions and history stay in Planning Poker Agility.
We already have SprintPoker. Does Planning Poker Agility get its features?
No. Each app keeps its own sessions and its own limits, even on the same 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.