Run incidents without leaving Slack
Tailored to your organization for smarter incident management
Confident, autonomous teams guided by automations
Learn from insights to improve your resilience
Build customer trust even during downtime
Connect everything in your organization
Streamlined incident management for complex companies
Run incidents without leaving Slack
Tailored to your organization for smarter incident management
Confident, autonomous teams guided by automations
Learn from insights to improve your resilience
Build customer trust even during downtime
Connect everything in your organization
Streamlined incident management for complex companies
Follow-ups play a vital role in post-incident tasks, enabling you to effectively track and manage tasks once an incident has been resolved. They serve as a valuable tool for learning from past incidents and driving continuous improvement.
With our newly introduced follow-up export templates, you can define how follow-ups should be exported to your preferred issue tracker, such as Jira and Linear.
For example, a Security team can utilise a dedicated Jira Project tailored to their specific requirements, while the Operations team can leverage a separate Jira Project with distinct fields and labels tailored to their needs. By employing follow-up export templates, you can effortlessly map incident.io fields to the corresponding Jira fields within these designated Jira projects.
This simplifies the process of exporting follow-ups to issue trackers. By saving valuable time, promoting consistency, and fostering a culture of thorough follow-up implementation, you can level-up your incident response. Go to Settings → Follow-ups → Export templates to set this up.
You can now define Slack channel naming conventions based on incident type.
For example, if you would like your security-related incidents to use a different naming structure from all your other incidents, you can now adjust accordingly! Simply configure within Settings → Incident Types.