Back to Changelog
Back to Changelog

December 7, 2023

Others

Incident Timeline Comments: Add Context and Move from Conversation to Action Seamlessly

Incident Timeline Comments: Add Context and Move from Conversation to Action Seamlessly

🗨️ Incident Timeline Comments: Add Context and Move from Conversation to Action Seamlessly

During an incident, new information is constantly coming to light and impacting our response, and we want to make it as easy as possible to capture information wherever you need it. That's why we're excited to introduce the ability to leave comments on timeline items when viewing incidents in Rootly's web platform! This is helpful for situations like:

  • Adding context or information to a specific timeline event
  • Attaching a conversation or task to a specific timeline event
  • Including images like screenshots in the incident timeline
  • Making notes when reviewing the incident's timeline in preparation for your Retrospective

This isn’t just your typical basic commenting feature—here’s what you can do with timeline comments in Rootly:

🧑‍🎨 Format your comments using markdown for added clarity, readability, and flair.
✏️ Made a typo? No problem. You can edit comments after posting.
🤳 A picture is worth a thousand words. You can attach files or images to your comments and they’ll be displayed inline right in the incident’s timeline.
✅ Surfaced a new to-do in a timeline conversation? You can quickly create a task or follow-up from a timeline comment.
🙉 Resolve comment threads to mark the close of a conversation (with the option to re-open if needed).

Check out this quick video of timeline comments in action!


🌝 New & Improved

🆕 Introduced new and simpler Slack commands for creating tasks and follow-ups. See the Rootly Slack Commands doc for an updated list of commands.
🆕 Teams API has been updated to be able to retrieve and update team membership.
💅 Streamlined onboarding experience for users provisioned through Okta. Users no longer have to re-enter their names and phone numbers. Rootly will match the values stored in Okta
💅 Follow-ups can now be created directly from the Retrospective tab. Users no longer need to navigate to the Follow-Ups tab to create action items when completing retrospectives.
🐛 Fixed display order on dashboard when sorting by severity.
🐛 Fixed issue with default custom field values not displaying on retrospectives.
🐛 Fixed inability to save phone numbers on Send SMS workflow action

Previous post
Previous post
You are viewing the latest post

Fields List View and More UX Improvements for Forms & Form Fields

Bulk Actions for Incidents and Workflows

Share and Set Permissions for Rootly Metrics Dashboards

Bulk Edit Task and Follow-up Action Items

Create Fully Custom Slack Forms Using Our New Form Builder

Specify Public vs Internal Incident Titles on Your Rootly Status Pages

Integrate with Multiple Instances of Jira and Confluence

Auto map any user from PagerDuty and Jira to Rootly incidents with new user lookup

Customize Your Incident Overview Banner in Slack

Improved Confluence Retrospective Templates

Workflows Can Now Automatically Update Previously Posted Slack Messages

Automate Component Status Updates on Statuspage.io

Rootly Joins the Vendr+ Marketplace

Assign Multiple Users to the Same Incident Role

Incident Triage: Investigate Potential Incidents Faster

Rootly + Fivetran Data Connector Integration

Less Noise, More Flexibility: New Slack Notification & Emoji Options

SCIM Group Support: Access Control Made Easy at Enterprise Scale

Integrate With External Systems via HTTP Client

Custom Google Doc Permissions

Advanced Slack Customization via Slack Blocks

Notion Projects Integration with Rootly

WhatsApp Integration

Manually Export Action Items to Ticketing Apps (Jira, Zendesk, Linear, and more)

Automated Dashboard Reports