You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hi, all
We have a few updates to Post Mortems to share with you.
Post Mortem related fields have been added to incidents. This means you now have greater control over tagging incidents that require a Post Mortem, and you can set a due date on the incident for when a Post Mortem needs to be completed by.
Label incidents that either require a post mortem or do not (the default is set to “Post Mortem Required”) from the details tab on each incident:
Add a due date for the creation of the Post Mortem from the incident details screen:
Once you have set these two fields, you can search for Post Mortems from the incident main screen. For example, use “postmortemStatus: published” to show incidents that have a completed Post Mortem:
Two saved search queries are also now listed for easy viewing from the incident main screen to better help you organize your Post Mortems and focus in on incidents that are closed but still need a Post Mortem created:
Let us know what you think about this new functionality and any other feedback you have on all things Post Mortems in the comments below, thank you!
Shaun Pinney
Product Marketing Manager, Jira Service Management
Atlassian
0 comments