Jeli enables you to tailor the product according to your unique incident response processes. Within your Incident Response Configuration you can customize the roles used in your response process, severity levels, and other Incident Response settings.

Define the roles that can be assigned in the the Jeli app for Slack. These roles can be assigned when an incident is started using /jeli open or updated during an active incident using /jeli set-<role_name>.

The default Incident Roles in Jeli are Incident Commander and Communications Lead. These roles can be edited to customize the name or Slack command alias, but cannot be deleted.

From the Incident Roles tab within your Incident Response Configuration settings, you can:

Select the Add Role button located in the upper right corner of the configuration page.

Let’s add a new role to Jeli, called the Scribe. From the Add modal, you can define the role name (Scribe), the alias responders can use in the incident channel to set the Scribe (/jeli sc or /jeli sc @Eva) and the help message to be sent to the Scribe when they are assigned.

Hit Add, and you will now see this new role displayed in your list of Incident Roles.

This new role will now show up in the Jeli Slack app on incident open, and the new role commands will be available during the incident (/jeli sc, /jeli set-scribe).

Select the three-dot context menu for the role you would like to edit, and select Edit.

Modify the role and select Update to save your changes.

Select the three-dot context menu for the role you would like to edit, and select Delete.

Confirm you would like to delete this role.

Broadcast channels help those who are not directly responding to an incident to stay informed. Each channel will receive a persistent message and subsequent updates as the state of the incident changes.

To add or remove default broadcast channels for your incidents, use the channel select to search for and select channels.

Define the severities that can be assigned in the the Jeli app for Slack. These severities can be assigned when an incident is started using /jeli open or updated during an active incident using /jeli sev.

Select the Add Severity button located in the upper right corner of the configuration page.

Now provide the name of your severity level, a shortcut to use in Slack and a description of what this severity level represents. In the below example we are adding Severity 3, which can be set in the channel either by the severity modal /jeli sev or the shortcut /jeli sev minor.

Select the three-dot context menu for the severity you would like to edit, and select Edit.

The order of your severity levels can be changed as well by dragging and dropping a severity level to a new position in the list.

Configure how often you want Jeli to remind the Incident Commander/Lead/Facilitator to update the incident status and the method you would like Jeli to use to remind them.

If the primary Jira issue is configured here, it will be created when an incident is opened using /jeli open. The incident name will become the issue title and the issue key will be part of the incident channel name.

For more information on our Jira integration for Incident Response, please see our documentation.

Select the project you would like your ticket to be automatically created on. Then, select a default issue type.

If you would like to disable the automatic creation of Jira tickets for incident response, you may clear the configuration on this page.

Hover over the Default Jira project field and select the X to clear the input.