Objective
As an incident participant, I can share a checklist with my team during an incident so that it’s clear what to do.
Assumptions
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 | |
|---|---|---|---|
| 1 | Give instruction on how to get involved | As a non-participant of an incident, I’m prompted to contact the commander if I want to get involved. | |
| 2 | Create checklist template | As a user, I can configure incident playbooks with a checklist to optionally save time setting up future incidents. |
|
| 3 | Change commander | As an incident participant, I can change the incident commander from the RHS so that it remains accurate. | |
| 4 | Log commander changes | As the incident plugin, a message is posted to the incident channel when the commander is changed. | |
| 5 | Track when a checklist item was completed | As a user, I can review when each checklist item was (last) completed so that I can identify the steps that are taking the most time. |
User interaction and design
Open Questions
Question | Answer | Date Answered |
|---|---|---|