Creating an Incident
- Creating an Incident
- Open a new incident: /jeli open
- Special options and integrations
- Add a summary to an incident: /jeli summary
- Add a severity level to an incident: /jeli sev
Open a new incident: /jeli open
Type in a name for the incident, select the stage your incident is currently in, customize the channels we broadcast your updates to and decide whether to set yourself as incident commander.
The only required field is the name, you can leave everything else as is and start the incident.
Upon hitting enter, a unique channel for the incident will be created with the naming structure:
#jeli-the-name-you-gave-it-1656373544. That number at the end is the Unix timestamp for when the incident was created, it helps keep the Slack channel names unique to give you one less thing to think about.
We’ll send you an ephemeral message confirming the incident has been created with a link to the generated slack channel. We’ll also notify your selected broadcast channels that an incident has been created.
Special options and integrations
- If you have set up your Zoom Integration with Jeli, you will also see the option to check or uncheck a box to generate a Zoom bridge when creating the incident.
- If you have set up your Jira Integration with Jeli, you will also see the option to create a Jira ticket on incident open. For more information see Creating/linking additional incident tickets.
Add a summary to an incident: /jeli summary
Type what you know about the issue so far and update it when anything significant changes.
The summary is the main description of the incident. It is displayed in the overview responders can use to get up to speed in the incident channel. As well as in the incident notification sent to the broadcast channels, where those not involved in active response can stay up to date on the status of response.
To quickly update the status without opening a dialog box use
/jeli summary [type out summary before hitting enter]
Add a severity level to an incident: /jeli sev
Select from the severity options of 0, 1, and 2, provide some in the moment context behind your decision and customize the broadcast based on the severity. Severity is not required and can be disabled by request.
To quickly set the severity without opening a dialog box use
/jeli severity [severity level number]
Want to know more? Go to the next doc in this series: Assigning Incident Roles