Jira Ops Early Access Program Update #4: Incident timeline improvements, see Jira Ops in action

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:

Just shipped: Edit and hide timeline comments

Your incident team can now edit and hide timeline updates in Jira Ops. This is a great way to make sure your timeline is a curated source of truth for the incident.

Not only does this help the team get up to speed and know what’s happened during the incident. But an accurate, descriptive timeline is your secret weapon during the postmortem. Here you’ll be able to easily understand what happened and when. You’ll be better prepared to spot the kind of changes that will cut down on future incidents.


Check out the documentation for full details on managing timeline updates.

See Jira Ops in action during our first webinar

Want to see an end-to-end demo of Jira Ops?

We’ll be showing the product in action during our first webinar on Dec. 6. “Get to know Jira Ops” will walk you through using Jira Ops with a team during a real incident, including:

  • How on-call engineers can kick off a response straight from alerting tools like OpsGenie

  • How integrations like Slack and Statuspage make incident response faster and more efficient

  • How to use the incident timeline to build a curated record of the incident

  • How to build the right remediation actions with better postmortems

We’ll also host a live Q&A after the demo. Even if you can’t make it for the live event, sign up and we’ll email you a recording afterward.

Check out the webinar

Take a look at postmortems

An effective postmortem helps you understand all contributing root causes of the incident, document the incident for future reference and pattern discovery, and plan preventative actions to reduce the likelihood or impact of the incident repeating itself.

From Day 1 we built Jira Ops with the postmortem in mind, because we know it plays such an important role in incident management.

At Atlassian we use Confluence to document our postmortems. Here the team can all comment, weigh in, and align on next steps.

We’re building out postmortems with a Confluence integration as our next new feature. Here’s a look at some initial designs. We’d love to hear what you think.

First up, you can see there’s a new action available on this issue now that the postmortem is resolved: “Create postmortem.”


From there, you’ll open a new postmortem template on a Confluence page. That postmortem document will now always be linked to the incident issue.


You’ll also be able to see postmortems across incidents and track which incidents still need a postmortem.


Finally, this PDF shows our current thinking for the postmortem template that will be populated from Confluence.

Post-mortem Template

We’ll be launching postmortems soon, but we’d love to hear your feedback or suggestions first.

Send feedback on postmortems

See you next week!





Log in or Sign up to comment
Community showcase
Asked Thursday in Jira Ops

I'm John Allspaw, Ask Me Anything about incident analysis and postmortems

I'm John Allspaw, co-founder of   Adaptive Capacity Labs, where we help teams use their incidents to learn and improve. We bring research-driven methods and approaches to drive effective inciden...

5,300 views 21 17
View question

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you