First look: behind the scenes building an AI incident responder.
Keep your workspace tidy by auto-archiving incident channels
January 10, 2022
It's the new year, and we're all ready for a change. Some of us have been tidying up and clearing out the cupboards - our CEO Stephen got rid of 6 bags of clutter over the weekend.
The same goes for the incident.io app: it's easy to forget to archive incident channels and they can sit around for months after the incident is over. So we're happy to introduce auto-archiving as our newest feature! We'll automatically archive incident Slack channels for you after either 7, 14 or 28 days.
You can enable auto-archiving in the Settings section of your incident.io dashboard, in the "Automation" section.
Note: We can keep your Slack workspace tidy for you, but make no promises about your physical workspace.
What we shipped
Here's what else we've been up to this week:
New
- You can now link an existing Jira ticket, Linear ticket or GitHub issue to an action or follow-up
- Incident list CSV exports now include incident duration in seconds
Improvements
- Auto-close now lives in the Automation section of Settings, next to Auto-archive
- When we auto-close, we'll auto-fill incident lead and summary if they're not set
- We can now show the content of pinned messages in the timeline after the incident channel has been archived
- Polished up the tutorial flow and improved some of the messages we send on install
Bug fixes
- Fixed removing a value in a multi-select dropdown, where it would remove all the selected values instead of just one
- Fixed a bug where timestamps wouldn't clear when you remove them from incidents
- Fixed the appearance of dialogs on mobile screens.