Post-incident reviews
Problem to solve
After an incident, users may need a space to conduct a post-incident review (PIR). We need to decide what the post-incident review should include, and where it should be located.
We concluded in https://gitlab.com/gitlab-org/gitlab-ee/issues/7821 that post-incident reviews need to be tightly coupled to the incident and easily accessible as a team works to resolve the issue. We want it to be immediately available upon resolution so that users are reminded and inclined to complete the post-incident review.
Intended users
https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/ https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/
Further details
We are conducting research to better understand users' needs and post-incident review requirements as part of ux-research#203 (closed). When this is concluded, we can use this issue to use the insights from this research to inform the design and prioritization of post-incident review.
Proposal
Current proposal (from https://gitlab.com/gitlab-org/gitlab-ee/issues/7821#note_173865935): if we continue using issues for incidents, the proposal is as follows:
We could have a Post-incident review section as part of the Incident template for the issue with some prescriptive instructions or links to post-incident review best practices. When the issue is closed, we could use a bot to add a comment to the closed issue (labeled 'incident') that reminds everyone who participated (any user to interacted with the issue) to complete the post-incident review section. This would be MVC.