Objective
As a user, I can refer to any past incident by reviewing them in a central place so that my team can use that information to make postmortem easier.
Assumptions
Requirements
Requirement | User Story | Jira Issue | |
|---|---|---|---|
| 1 | Access past incidents | As a user, I can see a list of all past and current incidents within the team so that the information is not lost. | |
| 2 | Archive channel when an incident ends | As the incident plugin, the channel is automatically archived when the incident ends so that it reduces clutter. |
|
| 3 | Download incident transcript | As a user, I can export channel transcript from the incident detail page so that it can be saved for record | |
| 4 | Inform participants that an incident has ended | As the incident commander, I receive an incident summary and a link to more info after ending an incident so that I know where to go for post-mortem. | |
| 5 | See a summary of each incident | As a user, I can see a summary of the following on incident detail page so that I can get the gist at a glance:
| |
| 6 | Access incident channel from the detail page | As an incident participant, I can go to the incident channel from the detail page so that I can comb through the conversation for post-mortem. | |
| 7 | See a timeline of how checklist was completed | As an incident participant, I can visualize the time gap between each checklist item so that it’s easier to identify which steps can be improved next time. |
User interaction and design
Open Questions
Question | Answer | Date Answered |
|---|---|---|