We’ve added a new ServiceNow integration to keep your incidents and follow-ups in sync between incident.io and ServiceNow.
For teams running their operations in ServiceNow, we know how important it is to preserve the structured record keeping you rely on. This integration closes the loop between fast-moving incident response in Slack or Microsoft Teams and the structured workflows in ServiceNow, so you get the best of both worlds without duplicate effort.
Engineers and responders can move quickly in incident.io without worrying about double entry.
Operations and compliance teams get full visibility in ServiceNow for reporting, auditing, and downstream workflows.
This release builds on our existing Catalog integration with ServiceNow’s CMDB. It’s ready to use today and can be enabled in just a few minutes (we timed it — three, to be exact!).
What's included
Incident records: Create a ServiceNow incident record automatically when you spin up an incident in incident.io. Just like our existing ticketing integrations like Jira and Github, you can do this for all incidents, or just those meeting certain criteria.
Live sync: Keep key details in ServiceNow up to date as the incident evolves, like changes to the name and summary and other fields.
Work notes: Automatically send incident updates with ServiceNow work notes, so it’s always clear what the status, severity and latest details are.
Follow-ups as tasks: Any follow-up actions you create are exported into ServiceNow as tasks. And if there’s a parent incident in ServiceNow, we’ll automatically link them too.
What else we’ve shipped
Improvements
Sentry issue alerts now include more details about the sentry alerts, such as the assignee
When using /inc escalate with the option to automatically route to different providers, we'll always escalate with high urgency to PagerDuty
We show a rate limit error when the rate limit is exceeded when performing a bulk operation
Bug fixes
Fixed a bug where we'd notify you about other parts of cover when your partial cover requests were accepted
We fixed a bug where clicking "Today" on the 1-day view of a schedule wouldn't take you to Today
We fixed a bug where navigating to teams that had a / in their external ID was constantly redirecting you
Fixed a race condition which would mark your Zendesk integration as broken
Fixed an issue where incidents wouldn't move to a closed status if all post-incident tasks were complete after deleting tasks
So good, you’ll break things on purpose
Ready for modern incident management? Book a call with one of our experts today.