Jira Ops Early Access Program Update #10: Why we added two more severity level options

[#1]

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!

• Jira Ops Early Access Program Update #7: Announcing postmortems for Jira Ops

• Jira Ops Early Access Program Update #8: Don’t miss this week’s Jira Ops webinar

• Jira Ops Early Access Program Update #9: Don’t miss tomorrow’s AMA with John Allspaw

New severity level options

We’ve added two new options for severity levels in Jira Ops.

Now, when you select a severity level you’ll see five different options to chose from.

1 - Critical
2 - High
3 - Moderate
4 - Low
5 - Informational

The change comes from user feedback. We want to give you options to manage an incident process that works for you. Previously only three severity levels were available, but you can certainly continue to use fewer levels if you prefer.

We’ve put a lot of thought into severity levels and how we use them at Atlassian. You can check out our incident handbook to learn exactly how we manage sev levels for major incidents.

Check out the handbook

Coming soon: Raise incidents directly from Slack

We’ve gotten a lot of feedback from users that being able to raise incidents directly from Slack would be helpful.

We definitely agree, and we wanted to let you know that this is something we’re currently exploring. If you have suggestions on how this should work or what you’d like this feature to include, send us a note and we’ll have a chat.

Let’s chat

See you in 2019!

With the holidays coming up, we know a lot of folks are taking time off. So are we! We’re going to take a holiday break from these weekly updates for the next two weeks. We hope you enjoy a relaxing, incident-free holiday and a happy new year. If you’re on call, Godspeed.

Onwards,

Matt