Page Comparison

...

Teams use messaging as the central hub for collaboration during time-sensitive situations
Teams use a dedicated channel to organize incident-related messages
Commanders are willing to start and end incidents from within messaging

Requirements

	Requirement	User Story	Jira Issue

Notes

1	See active incidents without leaving messaging	As a user, I can view a list of active incidents within my team in the RHS so that I get an overview of what’s currently happening.
2	See active incident detail without leaving messaging	As a user, I can select an active incident in the RHS to view its detail so that it’s accessible from anywhere.


3	Find the conversation related to an incident	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.
4	Know who’s the main contact for each incident	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.
5	Start an incident from without leaving messaging	As a user, I can start an incident within my team with a slash command, RHS, or post action so that response can start quickly.
6	Have a commander for every incident	As the user that starts an incident, I default as the commander so that ownership is clear.
7	Auto-create a channel for every incident	As the Incident plugin, a new channel is automatically created when an incident starts so that there is a place to log activities.
8	Choose the incident/channel name	As the user, I can choose the name of the new channel so that it’s easily recognized
9	Log incident start and end time	As the Incident plugin, a message is posted to the channel when the incident starts and ends so there is a timestamp record of who made the change.

Question	Answer	Date Answered