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.
I'm working on creating an Incident Management process. I noticed that there's a Post Incident Review queue in the IT Service Management project as well as various Incident Review templates in Confluence.
After an Incident Ticket has been created by the end-user and it's been serviced, is it better/best practice to have the Post Incident Review as an Issue/Request Type that is created and lives in the IT Service Management project under Post Incident Reviews Queue, or should this be created as a Confluence page?
Thanks!
Hi @Kevin Nguyen ,
PIR's (Post Incident Reviews and not to be confused with Post Implementation Reviews from the Change Management process) are actually a new part of the JSM template.
https://support.atlassian.com/jira-service-management-cloud/docs/what-are-post-incident-reviews/
Before that I would have thought it best to link a Confluence page but normally this new feature in the JSM project should handle it within the Incident ticket itself as a more integrated solution.
Awesome, thanks Dirk! That makes sense to me as well, keeping it all in the Service Management project.
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.