Mitigate an Incident

Jeli Part of PagerDuty

Set an Incident’s Stage to Mitigated: /jeli stage

Enter /jeli stage to move a Jeli incident to the mitigated stage. This will also create a Jeli Opportunity for when you’re ready to begin your incident review. Once you supply an optional reason for the stage change, you will receive a prompt allowing you to rename the incident using all the information you've gathered during the incident response, as well as provide a new summary.

/jeli stage command

/jeli stage command

📘

Slack Channel Name

Changing the name of the incident will not change the name of the associated incident channel in Slack. To change the name of the Slack channel, use /jeli rename.

The new name and summary will be included in the opportunity created in Jeli, as well as updated in the broadcast channels in Slack. Moving an incident to the mitigated stage also means we will no longer send you status update reminders on your set intervals.

📘

Important Note

Moving an incident to the mitigated stage is not required to close it, address followups, or create a Jeli opportunity. If you skip this stage, Jeli will still prompt you with those items upon closing. You can also move back into the identified or investigating stages from mitigated and continue response if need be.

Status reminder intervals will be restored if you return to either identified or investigating stages.

Address Followups

When an incident is moved to the mitigated stage, we send the list of follow up items to the incident channel. You can choose to schedule a reminder on a followup and we’ll notify you again about at the date and time you choose.

Schedule a followup

Schedule a followup

You can also mark the followup as done, edit it to add more details, or schedule a reminder to notify someone else about the item.

📘

Tip

Scheduled reminders for followups will not ping to remind you if the followup is marked as done, marked as ignored, or after the incident is closed.