Easier migrations from PagerDuty and Opsgenie

Mirroring schedules from PagerDuty

Many times, when an organization is testing On-Call, they aren’t always able to test out all our scheduling functionality because they will still need to use PagerDuty until they can run a full migration over to our product. This can be quite disappointing as our scheduling, cover requests, and overrides are quite nice to work with, if we do say so ourselves 😉

So, we’ve built out the ability to mirror schedules from incident.io to PagerDuty. This allows you to use the sparkliest bits of our product and have that reflected into PagerDuty until you are ready to fully migrate to our product.

If you’d like to see this feature for Opsgenie as well, let us know!

Bulk import schedules from PagerDuty and Opsgenie

While we could import schedules directly from PagerDuty and Opsgenie for a long time now, we now allow you to bulk import. This is a great timesaver if you have loads of schedules you want to import at the same time.

What else we’ve shipped

Improvements

Slack On-call notifications will now include more information about the alert
Within the Confluence / Jira settings pages, it’s now more obvious that the app is installed via Atlassian's marketplace
Searching users in the Settings page now loads the search results more quickly
If there are too many attachments to display in Slack, /inc attachments will send you to the dashboard for a better viewing experience
In our Splunk alert source, you can now select between the search name and the search ID as the deduplication key
Searching for a user to add to a schedule or escalation path now lets you search by email address, and shows the best-matching results first
When testing a workflow, parameters can be left unset
Made it clearer that workflows won't run on private, test, or retrospective incidents by default

Bug fixes