Back to Changelog
Back to Changelog

May 18, 2023

Action Items

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

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

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

The ability to auto-create issue tickets from action items has already helped many Rootly users reduce their manual work and increase productivity.

While it is easy to configure a workflow to create a ticket whenever an action item is declared, it does require a set of defined conditions to be met, before the task is executed.

As with many incidents, exceptions do occur - we are excited to announce a new feature that allows users to manually export action items ad-hoc to ticketing platforms such as Jira, Linear, Asana, Zendesk, Trello, Shortcut, and Freshdesk!

Here's what you can expect with this new feature:

  • Manually select action items to export: You can now manually select (even in bulk) which action items they want to export to your ticketing app. This gives teams more flexibility and control over what tasks are transferred, ensuring that only the most important tasks are added to your project board.
  • Fully integrated in Slack: Rootly is a Slack-first platform and we want teams to stay there during the entirety of the incident. Export of action items can be triggered directly in the incident channel or if preferred do it from the web platform on Rootly.com.
  • Flexibility to select projects on each export: You do not need to have a “default” project or board. Our new feature integrates seamlessly with ticket apps, giving you the ability to select any of the enabled project boards and their supported ticket types at the time of export. Individuals and teams can select their own project board directly.
  • Intelligent ticket type recognition: Already have a ticket for the main incident? We will dynamically present you with the option to export as a sub-ticket based on whether there is already an existing ticket for the main incident.

This new feature will give more control to Rootly users so they can manage their action items and stay on top of their projects - the way they wanted to.

GA today to all customers. Check out this short video to see the feature in action!


🌝 New & Improved

🆕 Added ability to enable password authentication on status pages created via Terraform
💅 Enabled option to select all when importing services from PagerDuty to Rootly
💅 Added overview_update_status_page_dialog to available action ids that can be used in Slack Blocks
🐛 Fixed bug on /incident list command to correctly return list of unresolved incidents in Slack
🐛 Corrected value mapping of {{incident.slack_channel_name} field for converted incident channels
🐛 Fixed wrong timeline timestamp for pinned messages in Notion retrospectives

Previous post
Previous post
You are viewing the latest post

🔌 Generic Webhook Alert Source

🔒 Lock Individual Workflows

🐦‍⬛ Round Robin Escalation Policies

🚨 Alert Sources

🔔 Configurable On-Call Shift Reminders

🪄 Dynamic Forms

🔐 Granular Role-Based Access Control Settings for On-Call

✉️ Emails as an On-Call Alert Source

🗓️ View Multiple On-Call Schedules Together

🤝 Partial Shift Overrides in Rootly On-Call

🏗️ Terraform + API Support for Rootly On-Call

🦉 Rootly x Thena Integration

🎬 New Full Platform Tour on Rootly.com

🔦 Drop-down Search in Escalation Policy Builder

🦊 GitLab Integration

Update Custom Incident Fields Using Workflows

🤖 Ask Rootly AI (+ More New AI Features!)

Rootly AI Editor: Fix Typos, Grammatical Errors, and Wordy Text Instantly

📊 Dashboard Sharing Permissions

✍️ Customize Your Wordbank for Automatic Incident Title Generation

🧠 Smart Defaults for Jira

🔌 The Rootly Plugin for Zendesk

🪄 Rootly Retrospectives

⚡ Command Palette: Lightning Fast Navigation with a Single Keyboard Command

Rootly Terraformer: Seamlessly Bring Workflows From Rootly’s UI to Terraform