Summarise Incident Timelines Automatically
Every morning, WebRun finds incidents that were resolved in the past 24 hours, reads the PagerDuty alert timeline and Jira ticket history, compiles a structured incident summary, and drafts it into a new Jira post-mortem ticket for your team to review and complete.
How can I automatically generate incident timelines for post-mortems?
WebRun assembles your post-mortem timeline automatically. Every morning, it finds incidents resolved in the past 24 hours, reads the PagerDuty alert history and Jira ticket trail, compiles a structured chronology with timestamps and actions, and drafts a new Jira post-mortem ticket - so your team starts the review with the facts already in place.
- Post-mortem drafts ready before the team's morning standup
- No manual log-scraping after an incident
- Consistent structured timeline format across every incident
Built for SRE teams · DevOps engineers · engineering managers · IT operations
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
app.pagerduty.comin a real browser with your saved login - no setup, no API keys. -
1
PagerDuty - read the incident alert timeline
pagerduty.com
WebRun opens PagerDuty to read the incident alert timeline. - Open PagerDuty Incidents and filter to 'Resolved' in the past 24 hours
- For each resolved incident, read the alert timeline: first trigger time, acknowledgement time, resolution time, and responder names
- Export the log of all updates and escalations
Done when The full alert timeline for every resolved incident is captured.
-
2
Jira - draft the post-mortem ticket
atlassian.com
WebRun opens Jira to draft the post-mortem ticket. - Create a new Jira ticket in your post-mortem project for each resolved incident
- Fill in the structured template: timeline, affected services, responders, contributing factors (blank for the team to complete), and action items (blank)
- Leave the ticket in 'Draft' status for your team to review
Done when A draft post-mortem Jira ticket exists for every resolved incident.
-
3
Slack - notify the team the draft is ready
slack.com
WebRun opens Slack to notify the team the draft is ready. - Post a message to #post-mortems tagging the incident's primary responder with a link to the Jira draft
- Include the incident name, duration, and resolution time
Done when Responders have been notified and have the Jira link to complete the post-mortem.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Will it publish or close the post-mortem ticket automatically?
No - the ticket is created in 'Draft' status. Your team fills in root cause and action items, then publishes when ready.
What if the same incident spans two days?
It uses the resolved timestamp to decide which run picks it up, so a long incident is captured the morning after it closes.
Can it pull in the Slack thread from the incident channel too?
Yes. Add your incident Slack channel to the plan and WebRun includes a link to the thread and a summary of key messages in the Jira draft.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.