Skip to main content

Enabling AI Iteration Summary Notifications

Enable AI-generated iteration summaries to keep your team aligned. This article explains how to turn on automatic notifications that summarize sprint progress and trends, delivered directly to your team’s Slack or Microsoft Teams channel.

Steven Silverstone
Updated by Steven Silverstone

The AI Iteration Summary Notification is an automated message that provides a concise overview of your team’s iteration progress. It is designed to keep everyone aligned without needing to check dashboards or generate manual reports.

Overview

When this feature is enabled, LinearB automatically sends a summary of your team’s current iteration to your configured Slack or Microsoft Teams channel at the end of each sprint. The summary includes:

  • Completed and in-progress work
  • Carryover and unplanned items
  • Blockers flagged during the iteration
  • Velocity trends compared to the previous sprint

This functionality is available per team and can be configured from the Team Settings - Autobots Insights tab.

Accessing Notification Settings

Only team admins or company admins can enable or disable this notification.
  1. Go to Settings in the LinearB app.
  2. Select the relevant team from the Teams list.
  3. Navigate to the Insights tab.
  4. Toggle AI Iteration Summary Notification on or off.

The setting applies only to the selected team. Each team can enable or disable the notification independently.

Delivery Method

Summaries are sent to the team’s default channel (Slack or Microsoft Teams), depending on your integration. A Slack or Teams integration must be configured for notifications to be delivered successfully.

Timing and Frequency

The summary is generated and delivered automatically at the end of each iteration cycle, based on the team’s configured sprint dates.

Example Summary

Team Iteration Summary – Team Autobots

12 Completed | 4 In Progress | 3 Carryover

1 blocker flagged this iteration

Velocity down 8% vs. previous sprint

[View Full Report]

How did we do?

How to - Handle Large Pull Request

Contact