It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

ANNOUNCING: Early access ITSM features in Jira Service Desk

Meet the new and improved IT service management template for Jira Service Desk! Here are a few of the powerful features ready and waiting for you:

  • Better focus on ITSM - clear ticket categories for incident management, change management, service requests and problems so your team can route and triage quickly and efficiently.

  • Respond faster to incidents - loop your team in and give context on any ongoing major incidents with the ability to link and escalate tickets to resolve incidents faster via a seamless integration with Opsgenie.

  • Deploy with confidence - keep a watchful eye over any deployments made through Bitbucket Pipelines or other third-party CI/CD tools, a change risk assessment engine and a services registry.

Bear in mind that early access means that this template is a work in progress, so we need your help to shape its future. If you decide to opt-in, please take a moment to hit the Give feedback button in the lower-left corner of your project and let us know what you like now and what you’d like to see in the future.

This early access template is currently only available in Classic projects. You can opt-out at any time by returning to the opt-in screen.

It's available right now! To opt-in, all you need is an existing Jira Service Desk Cloud site and Jira admin permission.

Go to <your site name>.atlassian.net/jsd-itsm in your browser.

This address will take you to a special page where you can enable the ITSM template on your site.

Click here to learn more about how to set up your new ITSM project.

For Jira Service Desk Server customers - As we get feedback from Cloud customers on these great new experiences, we’ll be bringing over the best and adapting them for Server and Data Center customers. The first experience you can expect is incident management capability. To hear more about what that entails, register for our Remote Summit (it's free!) and watch the keynote session called, "Atlassian Data Center: Building for change and scale." To learn more about the newest features on Server and Data Center, check out this blog: https://community.atlassian.com/t5/Jira-Service-Desk-articles/What-s-New-in-Jira-Service-Desk-Server-amp-Data-Center-Remote/ba-p/1338620#M249

Cheers and thanks for participating! 

17 comments

Another 'Cloud exclusive' feature? Great. Why are you actively alienating your oldest customer base more and more as time goes on?

Like # people like this

@Taylor Huston I hear you - the good news is we are currently building the incident management capabilities from this early access program in our Server and Data Center products. These should be available in the coming months! To hear more about what that entails, I suggest registering for our Remote Summit today (it's free!) and watching the Day 2 keynote session called, "Atlassian Data Center: Building for change and scale." 

Like # people like this

Thank you for supporting the Server based products!

Like # people like this
scott_boisvert Community Leader Apr 02, 2020

@Molly Bronstein Looking for the break out session "Atlassian Data Center: Building for change and scale", I'm not seeing it. Was it removed?

Like Văn_Buoi likes this
scott_boisvert Community Leader Apr 02, 2020

Nevermind, found it. Its not a breakout session its part of the Day 2 Keynote.

Like # people like this

@scott_boisvert thanks for that, I'll update above!

Like Văn_Buoi likes this

@Molly Bronstein  Is it (or will it be) possible to change an existing Service Desk Project to an ITSM project? We'd like to integrate our Opsgenie into our JSD setup. It's coupled right now with some webhooks/api/api gateway setup, but would like to use the native integration.

Like Văn_Buoi likes this

Classic projects only? Will you be improving what's in next-gen projects or are they already better than what's in Classic?

Like Văn_Buoi likes this

@Tom De Blende Hi Tom, great question! Unfortunately, we don't currently have a path to change an existing project in Jira Service Desk to the new ITSM project. This is something we want to get to in the future but at the moment we're trying to build the best functionality in this new project. Coming soon hopefully!

@DJ For now this new ITSM project will exist only in Classic projects. We're evaluating how it may work in next-gen projects but it's only in Classic for now. 

@Molly Bronstein thanks for your reply! Either converting a classic JSD project to ITSM or a clear migration path would be great. We are a long time Atlassian and Opsgenie customer. Tightly integrating both would be very nice. But as we have a large customer base using our Service Desk, starting from scratch as an ITSM Service Desk would be hard.

Like Liron likes this

Are there any plans to improve the U.I. and Documentation for existing products?

Is there a specific channel for providing feedback/bugs for ITSM preview project?

@Jason Sweet you can either hit the Give feedback button in the lower-left corner of your project OR you can email jsd-im@atlassian.com to provide feedback. Thanks so much! 

Like Liron likes this

I second Tom's comments on a conversion or migration path from existing Jira Service Desk cloud classic projects. I like the features indicated in the new template but need to know how to get from what we have now to the new template.

Like Patricia Francezi likes this

 

Hi @Molly Bronstein This looks great, but as I understand it, our existing JSD project cannot be converted to use this new template workflow. When will it be possible to migrate our existing instance, to use this new template? Thanks

Hi Molly,

Thanks for your very interesting announcement.

* I work for a non-profit / charity (on a pro bono basis like almost all of us do in this organisation)

* One of the initiatives we are looking to take forward is to develop our Jira based service management processes

* Those Jira based service management processes in our organisation are currently very basic

* We have Jira version v4.5.1 server edition with one project configured within Jira called "ITHELPDESK"

* ITHELPDESK is where we currently manage both IT incidents and service requests

* What I am hoping someone may be able to advise on is current best practice recommendations using Jira. Specifically:

1) This text above:

"Better focus on ITSM - clear ticket categories for incident management, change management, service requests and problems so your team can route and triage quickly and efficiently."

What does "ticket categories" mean in the stated context? Does it mean:

a) One category will be provided to mark which service management practice of incident, change, service request or problem management the ticket is relevant to? Or;

b) Within each service management practice of incident, change, service request or problem management, there will be different categories to choose within that practice?

On 1st reading I suspect that this means option a). However assumption is the root cause of many a misunderstanding. Hence I thought it worthwhile asking to make sure.

2) Is it recommended that:

a) incidents, service requests and problems are managed via the same Jira project? Or;

b) Incidents, service requests and problems are each given an individual Jira project

I ask in that the comments in this thread below seem to advocate using separate projects for each of incident and problem management:

https://community.atlassian.com/t5/Jira-Questions/Does-anyone-uses-JIRA-for-incident-problem-and-change-management/qaq-p/445857

3) I see that there is this Jira Problem Management workflow:

https://marketplace.atlassian.com/apps/1216179/problem-management-for-jira-service-desk?hosting=server&tab=overview

It is interesting to note that this workflow:

* Has no reviews at the weblink above

* Is listed on that weblink as "UNSUPPORTED"

* However the 'Support' tab states, "Basic support resources are available for this app."

* There are 2 version both released a week apart in 2016 Q3

* Hence if we start to use Jira as problem management tool:

a) Is that Jira problem management workflow in the weblink a stable product?

b) What level of support if any is available for that Jira problem management workflow?

c) Is that Jira problem management workflow currently a recommended product, given the nature of the original post?

4) I note comments by @Tom De Blende @kyle and @Minesh_Dattani enquiring about functionality to migrate existing Jira projects to use the new functionality mentioned in the announcement in the original post. Is there a ballpark timeline on when the migration functionality will be available for Jira Service Desk server edition? I ask in the context that given how embedded the organisation I work for is in the existing Jira technology that we have, it seems unrealistic for us to be able to migrate away from that without some sort of tool.

I hope this all reads in the intended constructive tone. Any help is very much appreciated (from anyone).

Comment

Log in or Sign up to comment
TAGS
Community showcase
Published in Jira Service Desk

The Complete Guide to Atlassian for ITSM

Hi Atlassian Community! This is Teresa from the Atlassian team. My colleague Paul Buffington @Buff and I are excited to share a brand new ITSM resource we’ve created – "The Complete Guide to At...

1,090 views 7 16
Read article

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