Deeksha Atlassian Team

Hi @Susan Waldrip , since status pages native to JSM are only available on enterprise tier, the features above are available only on the enterprise tier!

Hi All, We've shipped three new capabilities for Status Pages in Jira Service Management: "Send update to Statuspage" Automation Action -You can now post status-page updates directly from Jira Automation rules. Auto-post "Investigating" when a Sev1 fires, "Resolved" when it closes, or periodic updates on a schedule - no…

Hi All, We've shipped three new capabilities for Status Pages in Jira Service Management: "Send update to Statuspage" Automation Action -You can now post status-page updates directly from Jira Automation rules. Auto-post "Investigating" when a Sev1 fires, "Resolved" when it closes, or periodic updates on a schedule - no…

Hey @Patricia Francezi_iDev_ - Status pages native in JSM ( both public and private ) will be part of enterprise edition. 

Hi @John Funk We have integration action enhancement as next backlog items for extending this action. You can track updates from this ticket - JSDCLOUD-19172.

@Mark Hankins - I have replied on your early access ticket. If you have atlassian groups configured on admin.atlassian , you should be able to see them under private page status page access control settings. We can deep dive into your scenario to also ensure there are no permissions restrictions as well, since only jira…

@Josh we're eagerly awaiting your feedback! 

Hey @Mark Hankins , Apologies for the delay in rolling out the early access program. We have recently started enabling it for interested customers and you can read more about it here -…

Thanks @Dave Mathijs for calling out this capability. We do have it in our backlog, but I have also created a feature request that can be used to communicate more on this ask in the future!

Completely agree with you @Dirk Rosemann on status pages being underused and unleashing the capability to manage broadcasting updates, enabling self serve and streamlining the process to communicate on incidents! I have created a feature request for extending it to premium licenses, so feel free to vote and add your use…

Hi @Pierre Martignon , This is Deeksha from the product team and I just wanted to share that the team currently doesnt have any items on the roadmap since we are working on some broader level initiates like accessibility, integrating to the new atlassian billing system and much more! For feature requests to be picked up,…

Hey @Todd Thomas , Apologies I missed your query around the status page early access program! The program is open for Enterprise customers at the moment, however if the feature is of interest to you then please do Sign up here as it also helps us track if other plans are interested in similar capabilities!

hey @Greg D , That's a great callout! In the future, we envision stakeholder groups to have similar functionalities as teams as people might also want a single way to manage these entities which are essentially a bag of people. This might be a long term vision, and till we reach there we might take small steps like having…

Thanks @Rune Rasmussen for your questions. 1. I have created a feature request to sync Stakeholder groups to atlassian groups. We do not support this today since atlassian group has licensed users added to the groups, however stakeholder role can be assigned to users who do not have any paid license for the product. 2. We…

Hey @Josh , Yes, stakeholder groups are managed separately from atlassian groups and atlassian teams as the stakeholder groups can have external users also part of the group. Org admins can manage stakeholder groups from the JSM UI. Also any user added from JSM UI as a stakeholder will also be synced to admin.atlassian and…

Hi Jeff , For the first question, since you are using the JSM bundled with opsgenie, the transition timeline is different than the Opsgenie migration program listed above. You can create a support ticket to understand what dates you can exercise in case you want to reschedule your transition. Also during this transition…

@Darius Great question! We will update the document as well to have this information. Any external services configured will be moved to JSM and Compass, however creating new external services will not be supported. For you existing external services, you will continue to get alerts from statuspages subscribed to.

Hi @Lewis Vail , This is Deeksha from the product management team, I just wanted to share the relevant document to ensure the right configurations steps and resources were being used - https://support.atlassian.com/jira-service-management-cloud/docs/set-up-atlassian-operations-terraform-provider/ There is a new Atlassian…

Hi @Antonio Tarifa , Please refer to this document to migrate from Opsgenie terraform provider to atlassian operations terraform provider - https://support.atlassian.com/jira-service-management-cloud/docs/migrate-from-terraforms-opsgenie-provider-to-atlassian-operations-provider/

Hi @Bart Scheltinga , The tool automatically moves all your opsgenie teams and its configurations into operations enabled atlassian teams in Jira Service Management. 

Hi @Jeremy Stewart , 1. It is not possible to move certain features as all opsgenie features based on your plan will be synced with Jira Service Management. * To answer your problem of duplicate teams, all your opsgenie teams that have been moved over will have the opsgenie logo, so that you can identify which is your…

Hello @Tina Maddox , We have ensured that customers terraform configurations which rely on Opsgenie API's do not get impacted. Hence with the move, all your scripts and configurations will continue to work. Updating a caveat here that the terraform configurations using Opsgenie Team API's will continue to work only for…