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
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.
Does anyone know what the expected functionality/behavior of the Default post-incident review template, found within Project settings > Incident management > Post-incident reviews, is supposed to be?
Yesterday I enabled the Post-incident reviews work category, created a request type I titled Create a post-incident review, and had the system automatically create the [System] Post-incident review issue type. Within Project settings > Incident management > Post-incident reviews I connected my project to a Confluence space and selected a parent page for the exported post-incident reviews.
I then followed this Atlassian documentation to create a PIR from an existing incident issue, and publish it to Confluence. I assumed the published PIR page would be formatted like the Default post-incident review template, but my assumption was incorrect. Instead the page was laid out in the following manner.
I re-read through Atlassian's documentation but wasn't able to find anything describing how this Default post-incident review template is supposed to function. I did find this somewhat related Atlassian community question, where @Joseph Chung Yin provides a screenshot which shows the Default post-incident review template populated in the Description field during issue creation. When I created the PIR, there was nothing added to the Description field, and I created several more to test and the Description field was empty for each PIR I created. I can add Description to the request form, hide it, and add the template as a preset value, but is that the intended functionality? Or is that template supposed to automatically be added into the Description field?