Content Comparison

As an admin, I can install the Incident plugin on my server so that all users can access it.

As an admin, I can disable the Incident plugin so that users can’t access it but its data isn’t deleted.

As a user, I can start an incident with a slash command so that response can start quickly.

As a user, i can end an incident with a slash command within the incident channel so that it no longer shows up as active. As a user, I can view a list of active incidents in the RHS so that I get an overview of what’s currently happening.

As a user, I can select an active incident in the RHS to view its detail so that it’s accessible from anywhere.

As a user, I can see and click on the channel associated to an incident in the RHS so that I can quickly navigate to it.

As a user, I can view the commander of all incidents in the RHS without opening it so that I know who’s the point person.

As the user that starts an incident, I default as the commander so that ownership is clear.

As the Incident plugin, a new channel is automatically created when an incident starts so that there is a place to log activities.

As a user, I can choose the name of the new channel so that it’s easily recognized

As the Incident plugin, a message is posted to the channel when the incident ends so there is a timestamp record of who made the change.

As the Workflow plugin, incident start is available both as a trigger and action with channel name as a parameter so that it can be automated.

As a user, i can change the stage of an incident within the RHS so that its current status is clear to everyone else.

As a user, I can see the current stage of the active incidents in the RHS without opening it so that I save a click.

As a user, I can see how long it has been since the incident has started in RHS so I can put its urgency in context.

As a user, I can configure the incident playbook with specific stages using code so that they can be set for future incidents.

As the Incident plugin, a message is posted to the incident channel when the stage has been changed so that there is a timestamp record of who made the change.

As the Workflow plugin, incident stage change is available both as a trigger and action with stage name as a parameter so that it can be automated.

As a user, I can check off items for an incident in the RHS so that it accurate represents the team’s progress.

As a user, I can add items to the incident checklist in the RHS so that the team can adapt to the situation.

As a user, I can remove items from the incident checklist in the RHS so that the team can adapt to the situation

As a user, I can see the checklist for each active incidents in the RHS it’s clear what’s been done and what needs to be done.

As a user, I can configure the incident playbook with a checklist using code so that it created for future incidents.

As the Incident plugin, a message is posted to the incident channel when a checklist item has been added, removed, checked, or unchecked so that there is a timestamp record of who made the change.

As the Workflow plugin, incident checklist item change is available both as a trigger and action with action and item description as parameters so that it can be automated.

As a user, I can see related messages from elsewhere automatically copied in the incident channel so that I have all the information that I need.

As a user, I can configure the incident playbook with conditions to copy messages elsewhere in MM so that context is centralized in one place.

As the Incident plugin, messages that meet the condition in the playbook are automatically posted in the incident channel so that users save time from doing it manually.