Welcome to your weekly Jira Ops Early Access program update, where we’re sharing news and updates on Jira Ops progress as we work toward our 1.0 release. If you ever want to drop us feedback or ideas, you can leave a comment on this post or shoot us an email: jira-ops-feedback@atlassian.com.
And you can learn more about Jira Ops and start using it for free right here.
For previous updates:
Jira Ops Early Access Program Update #1: Announcing our next feature and a new integration
Jira Ops Early Access Program Update #2: Let’s talk severity levels
Jira Ops Early Access Program Update #3: A closer look at Jira Ops & Slack
Jira Ops Early Access Program Update #4: Incident timeline improvements, see Jira Ops in action
Jira Ops Early Access Program Update #5: Why we’re reading every ticket you send us
Jira Ops Early Access Program Update #6: Three new ways to get a live Jira Ops demo!
Enjoy better postmortems with Jira Ops' newest feature
This week we’re thrilled to announce our biggest new feature since we launched Jira Ops: Postmortems.
Teams typically prepare a postmortem document with a blameless discussion on the contributing factors behind the incident. But we know that manually creating the postmortem documentation can be a hassle and easy to forget.
In Jira Ops, you’re now prompted to create a postmortem document in Confluence when your incident is created. The postmortem template contains the key areas that ensure all aspects of the incident are analyzed and understood:
Summary – an overview of the incident, including key details copied from the Jira ticket
Timeline – key events during the incident, using the Jira Ops timeline (more on this below)
Analysis – covers each stage of the incident: lead-up, fault, customer impact, detection, response, recovery, and recurrence.
Root causes – the underlying causes of the incident, often determined by a Five Whys exercise
Lessons learned – what the team identified they should do differently next time
Actions – links to remedial tasks in Jira, to address the root causes and lessons from this incident.
The incident timeline is automatically included as a macro in the postmortem Confluence page. The timeline provides exact timestamps for all the important events in the incident.
See it in action: https://youtu.be/uC4Y2G6-YJ8
You can read more about postmortems in our announcement, and get started with Jira Ops today.
Onwards,
Matt
Matt Ryall
2 comments