You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.
View groupJoin the community to find out what other Atlassian users are discussing, debating and creating.
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
Jira Ops Early Access Program Update #10: Why we added two more severity level options
New timeline filters
You can now toggle between different integration updates to show on your Jira Ops timeline. By filtering the timeline to only show updates for certain tools, your team can more quickly get up to speed and find key details.
To see it in action, just click the “All updates” dropdown at the top of the timeline.
Improved incident templates
We’ve rolled out new templates for the incident description field.
Instead of a blank field when you open a new incident, you’ll see three headings already created here:
Customer impact
Mitigation plan
Suspected causes
We’ve learned a lot about the power of templates and processes during incidents. By prompting the response team with these headings, it will be easier to know what needs to be discovered and documented.
You can always edit these headings, modify them, add more, or delete them entirely if you need.
Note: This feature is currently available only for recently-created Jira Ops projects. If you have a project already established and you want these headings, shoot us a note and we’ll see what we can do.
Onwards,
Matt
Matt Ryall
Atlassian TeamScaling an agile organization and setting it up for success over the long term is a hard thing to do. We hear a common set of questions from customers all the time, questions like: Can agile scal...
Connect with like-minded Atlassian users at free events near you!
Find an eventConnect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.
Host an eventYou're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events
1 comment