We 💛 Google Docs
Many of our customers currently use Google Docs to write their postmortems. They enjoy the tooling for it's superior collaboration, ease of use, and familiarity as usually their entire company runs on it. However, when it comes to writing postmortems, although they prefer Google Docs, it's largely a manual process.
We are introducing our integration with Google Docs to automatically generate your postmortem after the incident is resolved. By enabling your Google Docs integration, Rootly will:
- Create a Google Doc under you desired Drive folder
- Populate the doc with a postmortem template as defined inside of Rootly (e.g. 5 whys)
- Populate incident metadata (e.g. incident title, severity, services impacted, resolution time, etc.)
- Generate incident timeline, no more copy-pasting from Slack!
- Disable native Rootly Dashboard postmortem experience and instead point users to Google Docs
🌝 New & Improved
- 🆕 Added a brand new Resources tab on the Rootly website. Everything from the hottest SRE jobs to our incident management blog!
- 🆕 Added a Genius Workflow task for auto archiving incident Slack channels
- 🆕 Export your incidents as a CSV
- 🆕 Added copy to clipboard option for postmortem timeline and incident data
- 🆕 After incident is resolved, users are prompted to edit their postmortem more explicitly
- 💅 Improved load times on Rootly Dashboard
- 💅 Improved reliability of PagerDuty integration that includes multiple redundancies
- 💅 Zoom, Google Meet, and other video conferencing options are globally turned on/off instead of per incident
- 🐛 Fixed issue where you could not unassign a user from an incident role in Slack
- 🐛 Fixed typos in
/rootly tutorialguide and in the Rootly Dashboard
- 🐛 Fixed bug where
/rootly tutorialwould not work for Slack users who had not linked their Rootly accounts yet
- 🐛 Fixed duplicate tags for key:value pairs that would occasionally pop up