Update released
Even when several scrum teams work within one company, estimation stays within the team. No notifications reach unrelated teams, and the confirmed result reaches everyone in the session, right there. In everyday use, too, actions now give clearer feedback and errors tell you why.
🃏 Scrum Poker estimation now stays within the team
When several scrum teams work within one company, a team’s estimation session would notify unrelated teams as well—and even let them see the votes. On top of that, you could press the start button on an item with no scrum team assigned, with nothing on screen to say why it couldn’t begin. The confirmed story point notification reached only the facilitator, and a button prompting people to join could linger even after the session ended.
With this update, joining, viewing, subscribing, and the start notification for Poker are limited to members of the scrum team the session belongs to. It doesn’t reach—or show to—anyone outside the team. On items with no scrum team assigned, the start button is now inactive and explains why: “Assign a scrum team to start.” And when a story point is confirmed, everyone in the session—not just the facilitator—now sees a notification that includes the confirmed value, and the issue where the join button lingered after confirmation is resolved.
A team’s estimation stays within the team, with nothing leaking or notifying unrelated teams. The confirmed result is shared with everyone on the spot, and the experience for existing members is just as it was—no extra steps.
✏️ Retrospective actions give feedback, and errors tell you why
Editing or deleting a retrospective card gave no visible response when you pressed it, and on failure it simply reverted with nothing shown. The message on a failed save was always the same—“Failed to save”—so you couldn’t tell a network issue from a permission one or a problem with your input.
We’ve now added in-progress indicators and success/failure feedback to editing and deleting cards. Error messages are unified into clearer, type-specific wording, and the same guidance applies to some other editing actions too—tasks, sprints, scrum teams, and more (in all four languages).
You no longer have to wonder whether an action went through, and when it fails, you know what to do next.
🔍 Closing a list’s search field while it’s empty no longer reloads it
In the product backlog, epic, user lists, and others, merely opening the search field—without ever searching—would reload the table when you closed it, losing the rows you were viewing and your scroll position, with flicker and a wait.
Now, if you close it without typing anything, it won’t reload. If you typed a search term to narrow things down and then cleared it before closing, it still returns to showing everything, just as before.
The rows you’re viewing and your scroll position stay put, so working through a list feels smoother.
📮 Contact us
If you have any questions or feedback, please don’t hesitate to reach out.
- ✉️ Email: info@on-your-side.llc