Workflow Versioning

🗄 Workflow Versioning

Introducing Workflow Versioning, a detailed audit trail and history of all changes made to a given Workflow.

Workflows are at the heart of Rootly. By making it easier to track changes made over time, teams will find Workflows even easier to manage and safely collaborate together than it already is.

Why? Previously, there was little to no visibility who made the change or what they were. Now there is a mechanism to quickly see what changes were made without needing to recall from memory and compare each Workflow attribute.

• Visually pleasing so at a glance changes from one version to another are obvious (e.g. colour coding)
• Version numbers and date changed
• User that executed the change
• The changes themselves track both past to present differences for all Workflow attributes (e.g. trigger, condition, task, etc.)

Existing customers can access this feature by heading into Rootly > Workflows > Clicking on any Workflow name > Versions.

What else shipped

• 🆕 Display in incident timeline all users that join the incident channel regardless if they’re a Rootly user
• 🆕 Ability to filter by incident attributes in Rootly API
• 💅 External postmortems on Confluence, Google Doc, Notion, and others display follow-up action items only, excluding tasks
• 💅 Fresh coat of paint for https://rootly.com/demo with accessible links to G2 customer reviews
• 💅 Naming for Rootly Incident Page is now aligned across both Web and Slack
• 💅 Ability to delete Rootly generated postmortems
• 🐛 Fixed issue where custom Workflow trigger commands in Slack weren’t working
• 🐛 Fixed issue where UI on Confluence and Google Doc postmortems had incorrect line spacing
• 🐛 Fixed issue where occasionally private incidents were accessible via postmortem view
• 🐛 Fixed issue where running /incident convert did not let you pin events to the incident timeline