From the new Incidents tab in Jeli you can
Filter and sort through recent and active incidents
Keep track of progress across multiple incidents at once
And view response details and updates outside of Slack
🔒 Private incidents are not displayed on the Jeli Incident View.
Filter, sort, and track multiple incidents at once
From the Incident index in Jeli, active* incidents will be displayed at the top of the page to easily see their stage, severity, how long they’ve been active, and who is coordinating response. Similar to
/jeli active in Slack, this can provide you with a dashboard to track the progress of multiple incidents at once, as well as indicate to unsure responders whether an incident has already been created for an issue they’re seeing.
Below the active incidents you can view the response details from all of your incidents. You can filter by words found in the incident title and/or summary, and by stage. The incidents can also be sorted by incident name and open date.
View incident response details outside of Slack
We know that every incident has an audience (which is why we make sure broadcast channels are flexibly configurable throughout response!) but we also know not every part of your organization lives in Slack.
Incident view is here to help keep folks up to date on how the response efforts are progressing by providing all the details typically sent to the broadcast channel, on a webpage. This provides a handy url you can send to stakeholders as an internal status page, and the link to the incident view is also available in the broadcast channel message. The information on this page will update automatically as soon as details are added or changes are made with the Jeli IR Bot.
The incident view is internal only, you will need to be logged in to your Jeli account to access the page.
At the top of the incident view you will find the incident details:
Incident Duration (time elapsed since the incident was opened)
and the most recent Status Update
Channels, Key Roles, and Resources
On the right is a block containing important links and who is currently assigned to each key role. This provides easy access to the Slack channels involved in response, including the dedicated incident Slack channel, and currently selected broadcast channels. As well as the Zoom or Google Meet coordination bridges, the primary Jira ticket created for response, and any relevant links attached to the incident via
/jeli link in Slack.
Events and Channel Members
Below the incident details are two tabs, Events and Channel Members. The Events tab contains all the updates being made to the incident as they happen, as well as who made the updates.
This events include:
Assigning (and reassigning) Key Roles
Updates to the Summary
The updates are in reverse chronological order, so the newest updates will be at the top, with progressively earlier updates below.
The Channel Members tab pulls the responders who have joined the dedicated incident Slack channel and adds the HR data you’ve provided to display their Name, Organization Role, and Group. It also includes a link to their People page in Jeli which provides rich historical data about their time spent in other incidents, which can provide insights into their areas of expertise and potential risk for burnout.