🔌 Integrate with Multiple Instances of Jira and Confluence

We understand the complexity that comes with managing incidents at enterprise scale. Organizations that are large or growing quickly often have multiple instances of Atlassian products like Jira and Confluence—especially if they've grown as a result of mergers or acquisitions. Having multiple instances allows for greater administrative autonomy as you can control who accesses which instances, and handle datasets differently based on your needs. As part of our continuous focus on delivering the most enterprise-ready incident management platform and feature set, we've launched the ability to set up multiple Jira and Confluence instances in Rootly.

With multiple instances configured, you’ll see a dropdown menu of your Jira/Confluence instances to select from in any workflows that interact with these integrations. This means you can automatically perform actions like:

• Creating a Jira issue automatically when a new incident is created
• Bi-directional syncing of action items from Jira to Rootly or vice versa
• Automatically creating retrospective timelines in Confluence
• Create a Confluence page within your Rootly Slack incident channel

…and more, in the instance of your choice!

To add another instance, head to the Integrations page in your Rootly web admin and click “Set up another instance” from your Confluence or Jira integration. Check out this quick demo to see how it works:

🌝 New & Improved

🆕 Replaced checkboxes with single-select field for marking incident kind as "normal", "test", or "backfill". The Create Incident form is now significantly cleaner and Incident Kind selection is much easier to understand.
🆕 Introduced dynamic count of filtered action items. Users will now see the count of action items change based on their filtered results.
💅 Optimized Audit Log page for better display. Now users will be able to see more data per page and cleaner data.
💅 Improved error response messaging on workflow failures.
🐛 Fixed inability to display Components field on web UI when publishing to Statuspage.io
🐛 Fixed loading error on available channels in a Slack workspace

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

Time to assembly (referring to how long it takes to get the right people together to solve a problem) is crucial in the early stages of incidents. Rootly can already create incidents for you from alerts in PagerDuty, Jira, and more, so you can move from detection to mitigation as quickly as possible. Now, we’ve removed another manual step by introducing the ability to map users in Jira and PagerDuty to their corresponding Slack account. This means that when an incident is automatically created from an alert in these tools, the reporter will be added to the incident Slack channel automatically as well. You can also specify if you’d like them assigned to a particular role, like Incident Commander.

This feature works by using a new User Lookup liquid variable: slack_id which you can use to configure workflows to auto-invite Jira Reporters and PagerDuty Agents. This can be set up using Custom Fields Mapping within the Workflow builder. Here’s a demo of how it works:

Need a hand getting set up? Reach out in your Rootly support channel. We’re happy to help.

🌝 New & Improved

🆕 Action Item Updated trigger now covers updates to the action item Type property.
🆕 Released new version 1.1.3 Terraform provider to allow opsgenie_id to be added to rootly_team resource.
💅 Enhanced form rendering logic to be able to recognize incident permissions and display only fields that the user has permissions for.
💅 Improved filtering capabilities on Metrics dashboard widgets to allow more complex conditions.
🐛 Fixed granular role-based access control bug where users with only private incident permissions cannot declare new incidents.
🐛 Added logging logic to ensure incidents moving directly from Triage to Canceled state have all mandatory timestamps logged.

🎨 Customize Your Incident Overview Banner in Slack

We’re all about details that add a personal touch. From choosing the emoji reactions you use to track timelines and action items, to creating highly customizable Slack blocks, we give you unparalleled control over how exactly you want to manage incidents in Slack. We’ve just added another touch of configurability by allowing you to upload your own banner image in the Incident Overview pop-up in Slack. By customizing your banner, you can ensure your brand's look and feel is consistently displayed even internally. It's another way that Rootly integrates seamlessly into your existing tooling and processes instead of feeling like an additional standalone tool.

You can upload your image in your Slack Account settings in Rootly (Integrations > Slack > Configure). You’ll see it when you click the ℹ️ Show More Info button from the pinned Slack message in your incident channel, or when you use the /incident overview command in Slack.

🌝 New & Improved

🆕 Incidents created by users with only private incident or only public incident permissions are now automatically set to the privacy setting that corresponds to their permissions
💅 Enabled URLs to display as clickable links in retrospectives created into Notion
💅 Public title on status page events can now be set independently from the template title and can be updated on subsequent publishings of the same incident
🐛 Fixed UI bug where the Create Incident button was not displaying when a user only has permission to create private incidents
🐛 Fixed sub-incident creation bug where updating severity unintentionally creates a normal incident
🐛 Fixed Status:500 error when loading workflow versions

📃 Improved Confluence Retrospective Templates

When an incident is resolved, Rootly automatically generates a Confluence page right from Slack with all of the incident’s key information populated in a clean, easy-to-read template. This way, you don't have to go scrolling through the Slack channel post incident to create your Retrospective timeline or track down post-incident action items. We just gave our templates a refresh so they’re even easier on the eyes. Here's what’s new:

• Improved visuals with color coding and emoji icons
• Action items and assigned roles are now included in the template by default
• Cleaned up timeline format for better readability

See Rootly generate a Confluence page from Slack in this demo:

Learn more about setting up your Confluence integration in our help docs.

Have a template you already love? No problem—Rootly can also populate your own custom Confluence templates.

Not a Confluence user? We have you covered too. We have a whole suite of integrations to generate retro docs including Google Docs, Notion, and Dropbox Paper.

🌝 New & Improved

🆕 Added new Object Name column to global audit log table so users can easily identify which workflow or incident each event attributes to.
💅 Searching for values in single and multi-select dropdowns is now more predictable and more consistent between Slack and web UI.
💅 Incident Updated trigger event now covers updates to the incident timestamps.
💅 Moved Custom Field mapping
🐛 Resolved issue with some users not being able to open the Manage Action Items modal in Slack
🐛 Fixed issue with Observers not being able to see custom fields on the Create Incident form

💬 Workflows Can Now Automatically Update Previously Posted Slack Messages

With Rootly’s configurable workflows, the app can automatically post to Slack when you take certain actions like updating the incident’s severity or status. We’re adding another degree of control here by allowing you to choose whether you want workflows to post a new Slack message or update a previous one. Choosing to edit previously posted messages helps you eliminate confusion from out-of-date messages in your incident Slack channel.

You can change this setting by enabling the “Replace Parent Message” option in workflows that post to Slack. With this option, Rootly will edit the previous message from the workflow instead of posting or threading a new message. When this happens, you’ll see text below the Slack message that shows that the message was automatically updated by Rootly, and at what time the last update happened. This reduces clutter in the channel and ensures responders don’t risk reading incorrect information from an outdated Slack message.

Here’s a quick video demo:

🌝 New & Improved

🆕 Retrospective are no longer locked strictly for post resolution—now they can be created and accessed during any phase of the incident
🆕 Assignees in Linear can now be automatically assigned via workflows
💅 Added the ability to auto-update incident when Jira ticket is updated
💅 Implemented guardrails to prevent non-stop loops on workflows
🐛 Fixed incorrect incident status and incident link display on Action Items metrics table
🐛 Addressed issue with cancellation messages not being logged in the incident timeline

⏱️ Automate Component Status Updates on Statuspage.io

We've made an exciting upgrade to our Statuspage.io integration: customers using Statuspage.io can now use Rootly to automatically update component statuses. Prior to this upgrade, teams that wished to mark a specific component as operational, degraded_performance, partial_outage, major_outage, under_maintenance, or offline, would need to manually publish to their status page. This upgrade enables you to simply set up your workflow(s) once, and Rootly will automatically publish to the status page and place each component in the correct status.

How it Works:

1. Connect your Statuspage.io account. You’ll simply need to link your statuspage.io account with your Rootly account once, and you're ready for configuration!
2. Import an existing status page. Use an existing page from your Statuspage.io account instead of creating a net new in Rootly.
3. Leverage the power of JSON and Liquid. The advanced setup section in the Publish Incident to Status Page task allows you to set the exact component(s) you want to update and the status(es) you want to set them to.
4. Automated task using a workflow. Once a trigger event occurs, Rootly automatically detects the change and updates the component(s) status(es) on your Statuspage.io page. This means your page stays up to date without any manual intervention.
5. Notify subscribers in real time. The workflow will also handle real-time notifications to keep stakeholders, customers, and internal teams informed on each status change.

Why it Matters:

• Improved Incident Response SLA: By automating status updates from Statuspage.io, Rootly ensures that the right people are alerted at the right time, reducing your Mean Time To (MTTx) metrics.
• Enhanced Transparency: Real-time system health updates foster transparency and trust with customers and stakeholders. Which in turn, enhances your reputation and overall customer experience.
• Increased Efficiency: Eliminating manual status updates allows your team to focus on incident resolution, rather than administrative overhead.
• Streamlined Communication: Consistent and accurate incident updates across all channels provides clarity during high-pressure situations.

Checkout this short video to see a sample use case and learn how to set it up:

🌝 New & Improved

🆕 Added user_id as an optional request body parameter to the Create a Incident API to allow teams to programmatically create incidents on-behalf of another user
💅 Added Cancel button to escalation dialog on web UI to improve visual consistency across all platform dialogs
💅 Improved user experience by dynamically displaying subscription options on status pages based on the enabled subscription methods
🐛 Fixed spotty Slack command responses for multi-org accounts integrated to Slack Enterprise
🐛 Fixed incorrect private user display in Slack incident channels

🛒 Rootly Joins the Vendr+ Marketplace

We’re making it even easier to get started with Rootly by joining the Vendr+ software marketplace, an invite-only program available only to the top SaaS products. In addition to the AWS Marketplace, Vendr+ provides another quick, streamlined option to purchase Rootly as your incident management platform. Vendr+ is available to the hundreds of customers worldwide who use Vendr to handle their software procurement negotiations.

Learn more about the benefits of using Vendr+ here.

🌝 New & Improved

🆕 Adding a Slack message to timeline via 📌 emoji can now be configured to only add the message to the incident timeline and not pin the message in the Slack channel.
🆕 Added subscription method grouping to the subscribers page of each status page. Now admins can easily identify how someone is subscribed (e.g. via email or phone).
💅 Updated status page notification email to be more reader-friendly.
💅 Updated ghost text in Scheduled Maintenance status page dialog to be more specific to maintenances.
🐛 Fixed UI bug where Services field was not displaying on the web UI.
🐛 Corrected {{incident.previous_attributes.status}} value to store previous values, not current.

👥 Assign Multiple Users to the Same Incident Role

By popular request, we’ve shipped an update to allow you to assign multiple users to the same incident role!

As always, this setting is highly customizable so you can choose which roles allow for multiple users. For example, you may want to be able to have multiple data analysts indicated during an incident, but only allow for one incident commander.

You can configure this under Configuration > Incident Roles. When you add a new role or edit an existing one, you’ll see an option to “Allow Multiple Users To Be Assigned This Role”. With this enabled, you can easily assign users to roles right in Slack.

Here’s a quick demo:

🌝 New & Improved

🆕 Rootly status page subscription options are now configurable
🆕 Added ability to define multiple HTTP status codes as success condition for HTTP Client workflow task
💅 Improved user experience by opening linked Slack channels directly in Slack, instead of opening in browser and then redirecting to Slack
💅 Backfill incidents are now supported in workflows
🐛 Fixed inability to clear previously set Severity field in Create Incident workflow task
🐛 Corrected In Triage At field to be an optional field on the Timestamps dialog on web UI

🚑 Incident Triage: Investigate Potential Incidents Faster

Start tracking potential incidents as soon as they develop, without the pressures of kicking off all the processes that come with declaring an incident. When you use the “In Triage” feature, we’ll create a triage incident while you investigate and get the right people in the room. From there, you can choose to update the incident status to “started” to declare an active incident, or “canceled” to track how the problem was resolved and close it.

Some benefits of incorporating triage status into your incident management:

• Capture incident data sooner
• Avoid duplicate efforts due to lack of visibility
• Reduce on-call fatigue from false alarms
• Create a greater sense of psychological safety around starting incidents

To get started with triage incidents, head into Configuration settings from your main menu in the web platform and navigate to “Forms & Custom Fields”. Click “Configure” for the form you want to add Triage to (this will typically be your “New incident” form to start out with), and add the “Mark as In Triage” field. With this field added, you’ll be able to create triage incidents in Slack or in the web platform just like any other incident, by simply toggling the “In Triage” option in the form when the incident is created.

Triage also supports its own set of workflows, so you can determine exactly what you want to happen when a triage incident is started. When creating custom workflows, you’ll find “In Triage” in the status options.

Check out a quick video demo of triage in action below and learn more about the benefits of this feature in our latest blog post.

🌝 New & Improved

🆕 Introduced Auto-Assign Role from On-Call Rotation and Invite On-Call to Slack Channel capabilities for VictorOps integration
🆕 Custom boolean fields can now be created with independent Name and Description fields
💅 Enabled liquid variables containing URLs to be clickable links in retrospectives created in Google Doc
💅 Up-versioned Terraform to v1.0.7 with a lot of improvements and fixed. See our Changelog.
🐛 Fixed the Page VictorOps On-Call task to allow paging via escalation policy or user
🐛 Fixed broken link on Integrations page for Statuspage.io docs

🔗 Rootly + Fivetran Data Connector Integration

Incident data provides valuable insights into the health of your business. Rootly provides plenty of built-in, customizable metrics right in the web platform, but for organizations that want to dive even deeper into their data, we recommend using a data connector to pull your Rootly data right into your centralized data location.

The Fivetran Rootly connector is a fully managed data integration for delivering real-time, efficient data replication from Rootly to your destination of choice. The ELT connector extracts a deep level of data from the source, replicates and loads that data in your centralized data warehouse or data lake, represented in an easy-to-navigate schema, where your analysts can easily access and query it alongside the rest of your organization's critical information.

See this quick setup guide for instructions on how to set up this data connector.

🌝 New & Improved

🆕 You can now use the Update a Google Doc task to update retrospective tasks and timelines in your own Google Doc templates
🆕 Action items manually exported to Jira are now accessible directly from the Rootly web UI
💅 Optimized response time on Export to Ticketing feature for a better user experience
💅 Improved retrospective timelines by removing distracting events such as user joining a Slack channel
💅 Removed query text on snapshot graphs retrieved from New Relic for a cleaner display
🐛 Fixed issue with auto-adding two identical code snippets on the Send Slack Block task
🐛 Fixed issue with the Subject field not being able to be left empty on Update a Zendesk Ticket task