Aditya Mani Atlassian Team

Hi @lee - The services that we are referring to here are JSM services. We will be migrating your JSM services without any downtime to a new experience. In case you are in the middle of a migration from Opsgenie to JSM, then those will also get synced automatically to the new JSM services experience. In short, you should…

Hi @Gerrit Wahlers - I am not sure I completely understood your question. I'll try to answer based on my understanding of your question. But please correct me if my inference is wrong: Groups synced from your identity provider (AD/SAML) via Atlassian Guard appear as standard Atlassian groups — they're just externally…

Hi @Aaron Koenig - That understanding is correct. Any paid license of JSM will continue having access to Services. This includes Standard, Premium and Enterprise.

Hi @David Washburn - To answer your first question, we do not have an EAP for this release. If you are an existing customer of JSM, then you will fall in the migration cohort, the details of which we will share with the community shortly. The timelines for migration will be around July. Also, about automatic discovery of…

Hi @Saki Okubo - If I am not mistaken, the screenshot you have shared is the screen that shows up in the configuration of a Jira work item Assets custom field. In this screen and setting, you should be able to reference the Services objects after the update. However, the "affected services" field continues to remain a…

Hi @Quang Kieu - Not at the moment. DX and JSM will remain in an un-synced state.

Hi @Lior Pinelis - * About the Compass sync - if you have Compass components synced with a JSM service, that sync will continue as is. Which means now the Services present in Assets will be synced with the Compass components. Further, any JSM service that could be added as an "Affected Service" to an Incident/Change will…

Hi @Dang Quang - * Unfortunately, we will not be enabling a sync between DX and the Services schema * In the new Services schema, the attribute types for the default attributes will be locked. So, you will not be able to add a new "Tier 5" in your example. But you should be able to create new custom attributes and assign…

Hi @Peter Miklian - At the moment, the services are excluded from the Assets limit.

Hi @Daniel Johnson - That is correct. We will support import via CSV and JSON and the other import channels already present in Assets.

Hi @Rune Rasmussen - This will have no impact on how change and incident management features will behave. From a rollout standpoint, currently this new feature will only be visible to new customers and signups in to Service Collection. We will be rolling out these changes to existing customers in the next couple of months,…

Hi @Lior Pinelis - this will have no impact on the "Affected Services" field in Incidents and Changes. The behaviour of this field will remain exactly the same, with some more benefits for the Service object itself like ability to add custom attributes, ability to add permissions to the service objects.

Hi @Benj Kamm - apologies for not being able to respond to this comment earlier. You can think of the Operations features as a platformised component between Compass and JSM. Both products will always be writing to and reading from a single source of truth. This also makes it easier for your IT teams in JSM and dev teams…

Hi @Harshitha Kandula - Apologies for the delay in getting back to you. Would you be open to chatting with me for a bit? I'd love to give you a quick demo of the capability and we can see how we can try to onboard you in to the EAP program. Feel free to set up time using this link :)