Product updates that make the retro loop tighter.

Teams can now choose the language for AI-generated summaries, action item suggestions, and analytics insights. Retro summaries count distinct attendees, voting shows remaining votes per section, external exports are admin-only with verified project access, monthly trials are 30 days, and blog unsubscribes now confirm.

• Choose a team-wide AI output language so retro summaries, suggested action items, and analytics insights come back in the language your team works in.
• Retro summaries now count distinct board attendees rather than only feedback authors, so the summary reflects who was actually there.
• Each section heading shows your remaining votes and updates live as you vote or unvote.
• Exporting action items to Jira or Linear is now limited to team admins, and project access is checked before an issue is created.
• Monthly plan trials are now 30 days long, giving teams more time to evaluate SprintPulse.
• Analytics and team action item pages preselect your organization and team when you only have one, so you skip an empty filter step.
• Unsubscribing from blog notifications now lands on a confirmation page, so it's clear the unsubscribe went through.

Smart Merge, action items, and retro summary suggestions became more accurate and better structured, and the feedback card layout stays steady as items are added, merged, or removed.

• Smart Merge, action item, and retro summary prompts are sharper, with structured output for takeaways, sentiment, and priority.
• Analytics prompts use consistent sanitisation so AI output is safer and more reliable.
• Feedback cards now use a dedicated layout engine so positions stay stable when items are added, merged, or deleted.
• Counters and the Smart Merge review prompt update correctly after deletes and merges.

Jira and Linear connections are more resilient, and the live retro flow is clearer around merge review, done status, reactions, and feedback cleanup.

• Jira and Linear access tokens refresh automatically, with clearer reconnect prompts when authorization really expires.
• Done status now makes it easier to see who is still wrapping up, including timer-end nudges for unfinished participants.
• Smart Merge review is safer before voting, with an option to skip the prompt once facilitators are comfortable.
• Feedback is easier to inspect and correct, with reactor names on hover and the ability to separate merged items.

Smart Merge now brings everyone along while the facilitator reviews suggestions, with better timer sync and tighter done-status feedback.

• Smart Merge suggestions can appear to participants in real time.
• Timer changes sync properly for non-facilitator admins.
• Reaction controls and done-status details are more stable on smaller screens.

Account security is stronger, with authenticator-app 2FA, backup codes, trusted devices, rate limiting, and audit logging.

• Authenticator-app setup with backup codes.
• Trusted devices can skip repeated 2FA checks for 30 days.
• Security changes create email notifications and audit records.

Retro action items can move into Jira Cloud with project, issue type, priority, and bi-directional updates.

• Export action items directly as Jira issues.
• Keep title, description, status, and assignee changes connected.
• Choose when an update should stay local to SprintPulse.

The retro room feels more synchronized, especially around facilitation, timers, presence, and AI-assisted grouping.

• More reliable presence and reconnection handling.
• Facilitator-led navigation is clearer for admins and participants.
• Smart Merge and action item suggestions are more useful.

AI grouping and analysis became more precise by using richer context from votes, comments, reactions, and facilitator decisions.

• Better confidence scoring for suggested merges.
• Improved action item suggestions with fewer duplicates.
• More context-aware sentiment and engagement analysis.

SprintPulse upgraded its AI capabilities to make summaries, grouping, and insights more helpful for real retrospectives.

• Stronger summary generation.
• Better topic extraction from retro feedback.
• More useful analysis for facilitators reviewing outcomes.

Sharing retro outcomes to Slack became smoother, so teams can keep follow-up visible where the conversation already happens.

• Improved Slack summary sharing.
• Better channel handling for team communication.
• Clearer feedback when Slack needs attention.

Retrospective summaries became more action-oriented, with better weighting of votes, comments, and reactions.

• Summaries account for engagement signals, not only text.
• High-voted and highly discussed items get more weight.
• Outputs better reflect what the team actually cared about.

The retro flow became easier to guide, with stronger facilitator controls and clearer real-time participant experience.

• Facilitator notes broadcast in real time.
• Participants get clearer state changes during the retro.
• The session flow is easier to follow from start to summary.