Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,293,413
Community Members
 
Community Events
165
Community Groups

Announcing: Incident Responders and Linked Alerts in Jira Service Management

THESE FEATURES ARE NOW AVAILABLE FOR ALL CUSTOMERS

---

Hello Atlassian Community!

Today, we’re excited to announce the rollout of two new incident management features in Jira Service Management Cloud to help you respond to and resolve incidents faster:

Use Alerts To Notify Incident Responders

You can now add, view, and remove multiple people and teams as incident responders directly from Jira Service Management.

Adding a responder will send a responder alert to the relevant user(s), notifying the right people to resolve incidents more quickly.

Alerts will also now be sent to assignees on incidents and the owners of any affected services added to incidents, as long as they have Opsgenie access and alert notification preferences set up.

Responders_Mockup timeline removed.png

For existing projects: Alerts are off by default, but admins can turn alerts on in their Incident Management settings page.

For new projects: Responder alerts will now be on by default for any new projects created in Jira Service Management.


Link Monitoring Alerts to Incident

You can now link and show monitoring alerts related to affected services directly from the incident view in Jira Service Management in order to improve information visibility for your incident response team and reduce time to resolution.


la.png


How do I get access to these new features?

These features will be available in your instance over the coming few weeks.

Keep a look out for the new Incident Management settings page in Project Settings to:

  • Find out how to add these new fields to your incidents

  • Turn on responder alerts for Responders and Affected Services

  • Assign your Opsgenie responder alert priorities to Jira Service Management incident priorities

These features are automatically enabled for any new projects created in Jira Service Management.

Questions or Feedback?

If you have any questions or would like to provide us with some feedback, leave a comment on this post and we will respond to you as soon as possible.

17 comments

Do these features require OpsGenie integration? Also, I assume that these new features are only applicable for Cloud instances of Jira Service Management and not for Data Center? Will we ever see any built-in features for incident management with Data Center?

Like Dan Brockwell likes this

Thi is great, can't wait to try it out! 👏

Like Dan Brockwell likes this

@Jennifer Flinn Hey Jennifer! If you have a merged JSM Cloud instance, Opsgenie automatically comes as a part of the product, so these features will be available to all such customers. These features are not available as a part of Data Center at this stage; I'll follow up with our JSM Data Center team to see what their plans are for incident management enhancements.

Like # people like this

Thank you @Dan Brockwell, it's much appreciated! We would love to hear more about anything coming for Data Center instances. It's always such a let down when a cool new feature is announced but there are no plans to enable for Data Center. 

Like # people like this

Fantastic to see some integration;

Is there any way to group tickets in ITSM utlising the teams field in Opsgenie.

Ideally I'd like to see the plan Team field linked with the Opsgenie Teams field.

Antonio

Like Dan Brockwell likes this

Hey @Antonio Biviano, glad the integration will be useful to your team!

Currently, there's no way to group JSM tickets by the Opsgenie teams field.

However, integrating the Opsgenie 'team' concept into JSM is something our product team is starting to explore; feel free to email me on dbrockwell@atlassian.com if you're keen to chat further about it!

@Jennifer Flinn Quick update on our thread of conversation.


At this point in time, we don’t currently have plans in the Data Center roadmap to enhance incident management capabilities.

Primarily, the team are focused on further integration of Insight asset management, resolving some SLA issues, bundling automation for Jira, and  shipping improvements to core request management workflows.

If you're interested, happy to put you in touch with the team owning this part of the product. Feel free to email me on dbrockwell@atlassian.com.

@Nikki Zavadska _jexo_ Glad you're as excited as us! Keen to hear what you think :)

Is this feature included in all JSM plans or just premium and above? 

Like Dan Brockwell likes this

@Dan Brockwell I think it's wrong of Atlassian to release new features like this unless it's made available across all platforms, unless of course there are technical reasons why that can't happen. 

Like pierre_ronnefalk likes this

@Sunny Kyusu I hear you, would understandably be frustrating for Server / Data Center customers. You hit the nail on the head; this decision is primarily down to technical reasons.

Our Server/DC and Cloud products have fundamentally different codebases and feature sets, so for the team owning Server/DC to rebuild similar functionality is quite complex and relies on underlying infrastructure that does not exist on those products.

If you have any further questions, feel free to reach out on dbrockwell@atlassian.com :)

Hello Atlassian team, @Dan Brockwell 

Thank you for introducing this feature and trying to improve the user experience; I have a couple of questions and challenges and need clarity on this.

So, I am a Jira admin, and I have been waiting for these features for a long time as our project was deployed last year and had an old template; I enabled these features as soon as I got notified! But I have the below issues.

1. Whenever I open an Incident, I see this popup with a message posted below; refer to the screenshot too: 


Update incident
This Incident is missing some features. Update the Incident to use the responder's field, linked alerts, and more. Learn more about updating incidents.
Update incident

** Users are complaining about this, and one user wrote this feedback:

I hope you are having a great day, and thank you for your help in advance. For the past week or so, whenever I view a ticket in the Jira project "INC," I see a popup requesting to update the ticket to the new version. Can you update all the tickets in this project so that the popup goes away? It is eating seconds to close it. Not to mention it stays on the screen, impacting readability until it is closed. 

** So I followed the instructions on one of the tickets and tried to understand why this pops up on the screen for issues created after we enabled the features still says you need to update the ticket to use new features; this looks like a serious issue. What I have done so far:

I followed this article and have already tagged my request types to incidents / Ticket types :
Customize the types of incidents your project will use. These will appear in your project navigation under 'Incidents.'
Make these request types available in your customer portal by editing your
portal groups.
.

See attached screenshot for reference!

** Bigger problem, when I create a ticket using Opsgenie integration on my JSM project, the alert that triggered the Incident is not auto-linked, but the same issue key is auto-linked to Opsgenie alert under 'Extra properties,' but when I try to link the JSM ticket on Opsgenie it doesn't work! This means opsgenie is also not building that relationship.

So all the new 'Incident' created under my Incident, do I need to update all existing incidents to have new features enabled, and how can this work for all newly created 'Incident'Screenshot 2021-10-07 at 13.19.04.pngScreenshot 2021-10-07 at 12.42.04.png

Like # people like this

May I know if we could only add users with Jira Service Management application access as Responders? Could we add Jira Software users as part of the responders too? 

Like Olli Suokas likes this

@Dan Brockwell Could you confirm what Wilson Seow asked, can we add any Jira user as a Responder or does that user has to have JSM product access?

Thanks!

This is a really good feature, however it would be really handy if you could somehow edit the information in the alert to give you more specific information at first glance. Currently the alerts states the ref/Project ref then Incident raised. If the summary of the incident could be included in this alert it would reduce a number of clicks and give you exactly what you were looking for and allow you to prioritise...

@Dan Brockwell Hey, Thanks for introducing new features. Just spent half day trying to adopt this feature to create "Assignment Groups" (https://jira.atlassian.com/browse/JSDCLOUD-106) , but seems to be a bit different. 
Just wondering if there was any thinking done to address the topic from the link? If yes, any blogpost or best practice to check?

Bit of background: Trying to adopt JSM to be used in major events (Games, Expo, etc.). People are working on shifts so there are no way to do personal assignments. Usually 150-600 resolvers, 50-250 assignment groups. 

Comment

Log in or Sign up to comment
TAGS
Community showcase
Posted in Jira Service Management

Jira Service Management Documentation Opportunities

Hello everyone, Hope everyone is safe! A few months ago we posted an article sharing all the new articles and documentation that we, the AMER Jira Service Management team created. As mentioned ...

176 views 0 4
Join discussion

Community Events

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

Find an event

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

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you