Dave Parrish [Atlassian] Atlassian Team

Hi @John Medina - Regarding your question about what classifies as a "build" - Yes, you've got it right. Specifically, we're listening for GitHub's workflow_run event, which occurs when a workflow finishes. We only listen to this event on the default branch of the repository. When that happens, we register a build event in…

Hi @Carolina Bravo 👋 It's Dave from the Statuspage product team. You can see who created components by reviewing the Activity Log for your status page. Note that the activity log also captures a number of other events (not just component creation), so you will likely need to do a bit of scrolling / pagination find the…

Hey @John Medina 👋 You've spotted some changes with the GitHub integration that are so fresh we haven't even documented them yet! In recent days we've added some additional metrics that get automatically calculated for components that have a GitHub repository linked. The full list of metrics we calculate for GitHub are:…

Hey @Isaac Petersen 👋 It's Dave with the Compass product team. Currently, Compass filters out deployments that aren't targeting the `production` environment. So just update the `deployment` line in your script to read: deployment: production And you should be all set!

Thanks @John Medina for the additional context. We'll be adding native support for build success rate in GitHub very soon, so there's no need for you to dig further into the docs. I'll post a message back here when it's available.

Hey John 👋 It's Dave from the Compass integrations team. Welcome and thanks for this question. Sounds like you're looking to manually push metrics to a component based on the result of a GitHub Action. We've got instructions for setting that up here: Push metric values using a cURL command Meanwhile, we are continually…

@Heikki Vesalainen 👋 Yes, we are actively welcoming user feedback! The best way to get in touch is by clicking the "Give feedback" button at the top of your Compass screen. Or if you'd prefer, you can give feedback publicly by starting a topic here in Community. Either way, we'd love to hear your thoughts about the…

Hey @Ole Øyvind Skaaret 👋 It's Dave from the Compass product team. At the moment the Statuspage<>Compass integration only supports public status pages. I would love to learn more about your use case though - would you be interested in a quick zoom chat sometime? If so, please feel free to email me at dparrish at atlassian…

Hi @Michael Juarez 👋 It's Dave from the Compass product team. The GitHub integration needs write permission in order to create organization webhooks. This is the only write operation that the integration currently performs. Webhooks are used for listening to several types of events- * Push events - for handling changes to…

Hi @David Harper, sorry you encountered this issue, and glad to hear you were able to work through it. We would have expected the metrics to appear automatically, so it's definitely a bug, and we're actively working on reproducing it. Thanks for reporting it!

Hi @lprada , thanks for this question! Our Swagger UI integration only supports a single swaggerfile per component. My suggestion would be to separate this into 3 components in Compass. Would that be possible?

Hi @David Harper 👋 It's Dave from the Compass product team. At the moment there's not a way to change an existing component from one type to another. As you've discovered, it's cumbersome having to delete and re-create a component when you want to change its type. Sadly, that is the best way to do it. The good news is that…

Hey @choi! For that endpoint, make sure you're using the PATCH method (not POST). Does that do the trick?

Hey @Bryan Kennedy, sorry to hear you're having trouble with Compass access. If you can drop us a line following these instructions, we'll get your access activated ASAP: https://community.atlassian.com/t5/Compass-Alpha-questions/Didn-t-receive-an-invite/qaq-p/1813255#M12

Hey @matt_smith! Companies using Statuspage can choose to enable Slack notifications for end users. For example, you can see this on the Confluence status page at https://confluence.status.atlassian.com/ If your favorite status page isn't offering Slack subscriptions, you should reach out and encourage them to enable it!…

Hi @lprada, it's Dave from the Compass PM team. Short answer, we'll gladly take your feedback in either place! It's really a question of visibility. This community forum includes all the Alpha users of Compass as well as the Atlassian team. So if you want to make a public suggestion to that group, and have others benefit…

Hey @Bryan The Statuspage app will only send messages to Slack channels where it has been explicitly granted permission to do so. As part of the setup flow for subscribing to notifications via Slack, you are prompted to choose a channel where you'd like to get notifications. The app is only able to post to that channel,…

Hi @George Howitt , the acceptable values for component status are shown here (expand the "request body schema"): https://developer.statuspage.io/#operation/patchPagesPageIdComponentsComponentId Here's the full list: * "operational" * "under_maintenance" * "degraded_performance" * "partial_outage" * "major_outage"

Hi Asher, the option to skip confirmation is available via the authenticated API for all plan types. Here is the endpoint in question: https://developer.statuspage.io/#operation/postPagesPageIdSubscribers Just specify the optional `skip_confirmation_notification` parameter in the POST body, like this: { "subscriber": {…

Update: There's a new, authenticated endpoint to use for updating subscribed components. It's documented here: https://developer.statuspage.io/#operation/patchPagesPageIdSubscribersSubscriberId The endpoint referenced in Jake's earlier answer has been deprecated (see our post about abuse mitigation for details).

Hi @Asher Francis , it's Dave from Statuspage. The reason you don't see the API endpoint that Carmen refers to is that it was deprecated recently (see our post about abuse mitigation for details). Instead, you should use our authenticated API, which provides an endpoint for create subscribers. Here are the docs for that…

Hey @Nikita K. , it's Dave from the Statuspage product team. I will add a little bit to Carmen's helpful response. :) A subscriber is a person who has explicitly requested to be notified (by email, SMS, Slack or webhook) when your status page reports an incident or maintenance. Users who simply visit your status page, or…

Hey Tim! Are you by any chance using Jira + Slack to manage incidents? I'm a Statuspage PM and we're doing some exploration in this area - would love to chat if so.

Hey @Mirek , I'm a Statuspage PM and I would definitely love to hear more about your use case for Slack + Jira! If you've got 30min to spare it would be great to chat - please feel free to book us a time: https://calendly.com/dave-parrish-atlassian/30min

Hey there @Scott Moore , I'm a product manager on Statuspage and I'd love to hear more about your use case for connecting Jira issues to a dedicated Slack channel, particularly in the context of incident management. If you've got 30min to chat that'd be great - please feel free to book a spot on my calendar. :)…

Hey @Jack , I'm a product manager on Statuspage. It sounds like you want to use the REST API to update an existing subscriber to remove one of their subscribed components. You can do this by updating the subscriber via PATCH, as described here:…

Hi @Renato Ítalo , that's correct, there's no cost for this feature, as long as you are on an eligible paid Statuspage plan.

Hi @Renato Ítalo , it's Dave from the Statuspage product team. We have a beta integration with Localize that allows you to translate text on your status page into different languages. If you're interested, contact Statuspage support and we'll get you set up!

So, how about some examples of code that work in jQuery 1.8.x but not in jQuery 3.5.x? Here are a couple no-longer-supported methods you may be using in your custom code: .load() The .load() method has been removed. So if your custom code is binding an event handler to the "load" JavaScript event, and you're doing it like…

Thanks @Chase Wilson! I can add a little bit more commentary about this update, as well as give some guidance about what you might need to change, if anything. The jump from jQuery 1.8.x to 3.5.x is a big one, and there have been a number of breaking changes along the way. However, there's a good chance that your page will…