Use Changes During Incidents

Before you start

• Open either the incident command center or the changes feed.
• Be ready to look for recent changes before you jump to broader theories.

Do this

1. In the incident command center, review the recent change summary for the active incident.
2. Open Changes if you need the wider feed across repositories or systems.
3. Filter by system, source, repository, or time so you can narrow to the likely change window.
4. Compare the timing of deploys, commits, and branch activity against the first alert and incident timestamps.
5. Add a timeline entry if a change becomes part of the investigation or confirmed cause.

Check it worked

• The team can see whether a recent change is a credible lead.
• The incident record captures the relevant change context.
• Responders spend less time asking who deployed what and when.

If it does not work

• If the feed is too broad, filter by system first.
• If the change summary is empty, check whether the system is actually linked to incoming change signals.
• If a change was relevant, record it in the incident and retrospective instead of leaving it in chat only.

Next

• Run a retrospective
• Explore reports