Zeeshan_twdimt Atlassian Team

Hey @Walace Feres , Yes that is possible when you are using Azure AD SSO via Opsgenie login. Under Opsgenie Settings > Login and SSO > Azure AD you can enable the following option and then see the user role you can auto-provision the users with: Best regards,

Hey Tomas, Thanks for reaching out about this functionality. Though it is not possible at the moment, this suggestion has already been forwarded to our product team as a feature request. They are further gathering interest from other customers on it before exploring the possibility to implement it. I have gone ahead and…

Hey @Alexander Turbin , You can simply reach out via the Chat support on the bottom right of your Opsgenie GUI or via https://support.atlassian.com/contact/ BR,

Hey @Ste404 , Yes indeed you can use a tag format to change the incident status the following way: inc:prefix as stated in the documentation:

Hey @Alexander Turbin , I would suggest option b) as it would help keep all your configuration in one place and make it easier to manage your on-call. As for the 'integration fairness' yes we can apply that for you on our end, however, the percentage completely depends on your use case and how many alerts you expect from…

Hey @Yuly Buenahora , This information is available via the Opsgenie web app and mobile app for the users part of your Opsgenie account. You may navigate to 'Who is on-call' tab and click on the on-call user's name to see their contact information for both the webApp and the mobile App. Hope this helps answer your query.…

Hey @Erica Dohring , In that case I may suggest reaching out to Opsgenie Support team via https://support.atlassian.com/contact/ so we may request access to your account and investigate your case accordingly. Best,

Hey @Erica Dohring, In this case the alert that gets created with source (#1) is then suppressed and no notifications are sent for that as only the 'Responder' alert is responsible for sending out the notifications (Voice/SMS/Email/Push).

Hey @Erica Dohring , This is expected behavior. When you create an incident, it creates a Responder Alert for each user/team that is a responder on the incident. This is so that every Team/User meant to be notified of the Incident is notified via those Responder alerts. At the moment, it isn't possible to change this…

Hey @Michael Matthews , Yes that is possible, however, via the Notification policy, not alert policy, where you can define the filter as you have in your screenshot and then select the following option: You can adjust the number of minutes there accordingly. It is required for this to work that the those key-value pairings…

Hey @Chris Hills , There is no such implementation being worked on at the moment, however, you can create a Feature suggestion ticket for it on our Development team's dashboard via: https://jira.atlassian.com/secure/MyJiraHome.jspa Moreover, based on your use case, you can instead make use of OEC which allows you to run a…

Hey @Martin Reißner , We will need you to reach out to our Support team via: https://support.atlassian.com/contact/ so we can request access to your OEC configuration which contains private information (and this is a public platform) and then assist you accordingly. Best regards,

Hey @Logan Jacobson There is no such limitation on the notification, however, there is a limit on the number of subscribers you can have on your page. This count varies based on your Pricing Plan so you can adjust that by purchasing a pricing plan accordingly: https://www.atlassian.com/software/statuspage/pricing Feel free…

Hey @Maximiliano Flores, You may refer to our translation tool via the Localize app for your requirements. You may read further about it here: https://support.atlassian.com/statuspage/docs/translate-pages-with-localize/ Best regards,

Hey all! Recently I have had a few customers facing the same issue and the query shared above did not work for them, whereas the following query did: {{issueTitle}} | {{ eq "CLOSED" state yes='UP' no='' }} {{ eq "ACTIVATED" state yes='DOWN' no='' }} Hope this helps! Best regards,

Hey @cmanar-a , Thank you so much for your feedback and helping us make Statuspage a better product. I have forwarded it to our Product team as feature suggestion for the future with an internal ticket ID number STATUS-541 that you can use to receive updates from our Support team. Kind regards,

My colleague there means that the endpoints like ‘api.statuspage.io/v2/<endpoints>’ were deprecated. The Page API uses something like ’status.twilio.com/api/v2/<endpoints>', which is different than what was deprecated and is working as expected.

Hey @Nikita Nemykin We have two APIs: * Manage API: The authenticated API found at https://developer.statuspage.io/ for managing the page - this is the v1 API you are referring to. * Page API: An unauthenticated Status API for querying information from the page and embedding it elsewhere. The Status API can be found at…

Hey @Scott Palgon , Thank you for raising your query and yes you do need to have a separate set of credentials for accessing the 'Manage' site and the external Statuspage for an Audience-Specific Statuspage. You can be a part of the Team Members list for your page but if you are not part of the 'Audience' list you cannot…

Hey Eric, Thank you for your feedback and help improving Opsgenie. As of now, we are aware of this issue and have a public facing Bug ticket for it that you can track via: https://jira.atlassian.com/browse/OPSGENIE-1110 Please feel free to post any further queries/comments regarding this issue on that ticket as that will…

Hey @wworek , Thank you for your query! :D Enabling "Allow users to be auto-subscribed to every incident" does not mean that all users will be auto-subscribed to every Incident automatically, it is just that they will have the capability to choose to be auto-subscribed to all incidents. So for them to receive notifications…

This might be the Feature suggestion ticket you are looking for: https://jira.atlassian.com/browse/JSDCLOUD-9649

Hey Noah, You're right, marking an Incident as Major indeed does not have any effect on the alert. For more information on the workings of Major Incidents feel free to read the following documentation: https://support.atlassian.com/jira-service-management-cloud/docs/mark-an-incident-as-major/ Best regards,

You're most welcome! ☺️ 

For two separate pages all the configurations and incidents will be managed separately.

Hey Agnieszka, Please reach out to us via our Customer Support portal: https://support.atlassian.com/contact/#/ so we can check your account details and assist you accordingly. Best regards,

Hey Dragan, For page-viewers it is not possible to have multiple forms of Authentication for a Private Statuspage subscription. Please see our documentation to learn how you can set up Authentication for Private Pages: https://support.atlassian.com/statuspage/docs/require-saml-for-private-pages/ BR,

You're most welcome! :)

Hey Burak, A suggested workaround for your use case would be to create a Lambda function in your AWS which triggers the Opsgenie Maintenance API: https://docs.opsgenie.com/docs/maintenance-api and creates a Maintenance Policy in your Opsgenie for whenever your AWS instance is restarted. Since this is not an outright…

Hey Rajkumar, That is the Incident ID which is auto generated and has to be unique for every Incident. This is built in functionality of Statuspage and cannot be changed, however, feel free to open up a Support Ticket to us explaining your use case via: https://support.atlassian.com/contact/#/ so we can assist you further…