Comments
-
Nice breakdown. In my experience both work—pick what fits your team’s reality. When to use what: • Planning Poker: new teams, fuzzy stories, or when live debate clears things up fast. • Async Poker: distributed teams, big backlogs, less meeting time. Best combo I’ve seen: Run a quick async pre-vote over 24–48 hours,…
-
Hi @Afrooz Kasraei, if still relevant, please check GoAgile Online Planning Poker (Jira-integrated): https://goagile.ai — supports Jira issue creation/updates, CSV import/export, AI helpers for story context & acceptance-criteria checks, and other.
-
I’ve run into the same issue. After migrating to the v3 API, I also had to rewrite the Jira search paging module since it previously relied on start, end, and maxResults. The new Search API no longer supports those parameters, so I had to adjust the logic accordingly. Not sure if this helps, but thought I’d share.
-
Thanks, @Tarang it makes sense
-
Looks interesting, thanks for sharing!
-
If you just need something simple and remote-friendly, I’d look for tools that integrate directly via Jira OAuth and don’t require admin installs. One lightweight option worth checking is GoAgile.ai https://goagile.ai/ — it connects with Jira Cloud and adds a bit of AI support for faster, consistent estimates. If you must…
-
That’s a really interesting point — I think AI’s role in sprint planning is less about replacing human judgment and more about enhancing the quality of team discussions.In most Agile environments, the hardest part of estimation isn’t the math — it’s aligning different perspectives and historical biases.AI can help here by…
