Just a heads up: On March 24, 2025, starting at 4:30pm CDT / 19:30 UTC, the site will be undergoing scheduled maintenance for a few hours. During this time, the site might be unavailable for a short while. Thanks for your patience.
×I clicked in the "Learn more about post-incident reviews" link in the Features section of a JSM project, read the full text, clicked in Learn more about best practices for post-incident reviews, and still don't know anything about what the Post-incident reviews *feature* in JSM actualy does.
It is simply (?) a post-Mortem of an incident. You document what/when/where/how and improvements to avoid in the future. It is linked to your JSM incident for historical purposes. The article you referenced also leads you here - https://www.atlassian.com/incident-management/postmortem/templates
Thanks for the answer Jack. My question is exactly what advantages this new feature brings over using Post-Mortem pages in Confluence.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Ah, I see and fair question. My guess is simply a more integrated solution.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.