Better Slack Notifications, Smarter AI Summaries, and Enhanced Runbook Management

Hey there, firefighters 🧑‍🚒 Here's what we shipped for you this week!

💬 Incident Attachments Now Notify in Slack#incident-attachments-now-notify-in-slack

No more wondering if that critical screenshot or log file made it to the team! Incident attachments now trigger Slack notifications, keeping everyone in the loop when new files are added.

What's new:

Files uploaded via the UI or API now post to your incident Slack channel
Attachments from Slack reply in-thread to maintain context
New incident_attachments notification preference (defaults to silent to maintain existing behavior)
Better visibility for critical documentation during incidents

🤖 AI Summaries That Stay Current#ai-summaries-that-stay-current

Your AI-generated incident summaries just got smarter! They now automatically refresh when key milestones change, ensuring stakeholders always have the most up-to-date context.

What's improved:

Summaries regenerate automatically when milestones are updated
No more stale information during critical incident phases
More accurate real-time updates for all audiences

📊 Runbooks: See What's Actually Being Used#runbooks-see-whats-actually-being-used

We've completely revamped how you track runbook usage! The runbooks table now shows when each runbook was last executed and which incident triggered it.

New capabilities:

“Last Executed” column replaces the "Last Updated"
See which incident used each runbook with hover details
Sort by execution date to identify your most active processes
Sort by team to organize runbooks by ownership
Quickly spot stale runbooks that might need review

This makes runbook audits a breeze and helps you focus on the processes that actually matter to your team.

🎯 Clearer Milestone Configuration#clearer-milestone-configuration

Setting up incident milestones is now more intuitive with improved requirement displays that actually make sense.

What's better:

First milestones correctly show "Fields required at declaration"
No more confusing "previous milestone requirements" for your starting milestone
Each milestone clearly displays its specific field requirements
Visual hierarchy improvements make configuration straightforward

That's all for this week! As always, if you have any questions or feedback, our team is here to help. Keep fighting those fires! 🔥