Enrique Serrano Valle Atlassian Team

@Phill Pafford I added an answer to your other thread too, but you're right that there's an operation to delete event sources that were manually added available in the GraphQL API. Not sure about the 401 - I followed essentially your same steps with my username and token for that site and auth worked properly. (You'd need…

For manually-added event sources, you can delete them using the GraphQL API. Example: curl -X POST \ -u "yourUsernameEmail:your-long-api-key" \ -H "Content-Type: application/json" \ -H "X-ExperimentalApi: DevOpsBeta" \ -H "X-ExperimentalApi: compass-beta" \ -d '{ "query": "mutation DeleteEventSourceMutation { compass {…

@Phill Pafford that's good feedback; Compass might do this a bit differently. Here's a Compass-dedicated example that has useful guidance about external IDs for event sources. With an event source being a funnel for events of a given type (e.g.: deployments) that apply to (at least) one component, the external ID is…

Hi, @Phill Pafford ! Compass currently has a limit of 20 event sources per component. There are multiple ways that you could end with a Compass component with multiple event sources created. Some tools and flows create and attach them for you. There's more information about event sources…

@tobiassjosten thank you for the additional information. There may be a couple of fronts going on. JSM syncing Theoretically, the `synced-with-jsm` tag is meant to appear when a Compass component is created and a synced copy is added to JSM, or in the opposite situation (a JSM service is created, and then a synced Compass…

Glad to hear that removing the user-agent and the referer headers solved the 403s @Dima Slupytskyi ! It was the XSRF protection triggering then.

@tobiassjosten the "synced-with-jsm" label indicates that there's a corresponding component created in JSM that matches its Compass counterpart. They both should be linked. The creation of a new Compass component should be creating these new corresponding components in JSM. The "source:github" label is applying when…

@Dima Slupytskyi okay! Going through the logs, I think your request is getting rejected because of XSRF constraints. I'm not sure about why your specific setup is encountering this when some other sites attempting to do the same aren't seeing this situation, but maybe explicitly adding an origin header that matches the…

@Dima Slupytskyi that helps. Just double checking based on the sample payload that you've sent: have you also replaced `!id!` by the cloudId of your site when providing the metric source Id? I assume the line that you'd provide for that call would be: \"metricSourceId\":…

Hi, @Dima Slupytskyi ! You're right that Compass admins have permissions to push metric values to metric sources attached to components, as described in https://support.atlassian.com/compass/docs/how-do-compass-permissions-work/ It is possible to set up more detailed permission policies and restrict who can update metric…

@tobiassjosten got it. I am not sure either about how we arrived to the original situation (I suspect the original mechanism to create the components might not have been a manual repository import), yet we're working on solutions that would prevent this situation coming up in the next quarters. For your specific case at…

@tobiassjosten thank you so much for reaching out to us and sharing your experience with the re-importing of components and repositories. We appreciate your feedback, as it helps us improve the product and serve you better. The system is designed to prevent duplicate imports of repositories that were originally created via…

@tobiassjosten I hear you - when you're seeing the "Configure" option in your application, and you don't see any option to import in the GitHub app page in Compass, it can be a consequence of a different Compass site being connected to the same GitHub organization, or your current connection not being in a functional state…

@Arun Subramaniam-a there was a condition that caused some users to not have a functioning import button for GitHub in Compass. That situation was remediated Dec 10th 2024, so please let us know whether you still need any help!

@Andrew Bruno @Michael James good call on the allow lists. Compass integrates with GitHub via a Forge app. You can find the IPs that Forge apps use in this link, tagged with "forge". This document has some additional information and context as well about the IPs that Atlassian uses.

Hi, @Andrew Bruno , @Michael James , thanks for reaching out. You're correct that free Compass versions should have a template creation enabled once an SCM app is installed and configured. I assume you're clicking the "Templates" section in the main navigation bar to access template creation? If you're using the GitHub app…

@erwin_de_groot I hear you; the organization admin permissions and the Compass admin permissions manage different access constraints (even when the former can allow you to update the latter). I'm glad that this allowed you to complete the configuration. Thanks to your feedback, our engineers are also working on an update…

@erwin_de_groot I think I was able to reproduce the redirect from "Configure" to the general marketplace apps page (instead of directing straight to the app management screen), so thanks for pointing that out. While our engineers look into that, here's a workaround: in the marketplace discovery page, you should be able to…

Hi, @erwin_de_groot! To install and configure Compass Apps, you need to be a Compass Admin. If you had installed the "Bitbucket for Compass" App in Compas yourself, maybe your permissions have changed in the meantime? Can you verify that you're a Compass Admin, or that a Compass Admin in your organization can click…

@Alexander that's an even better idea. The approach that you're suggesting would work perfectly.

@Alexander thank you for the update. The config-as-code functionality of Compass wasn't initially designed to work with monorepos, but we are currently working to improve support for them. I can see how a big set of files changed, including several compass.yaml files, could have caused component creations to be missed.…

@Jeff Madison here's the official announcement for the feature! https://community.atlassian.com/t5/Compass-articles/Announcement-Admins-can-now-review-and-approve-components/ba-p/2815700

Hi Mario, Thank you for reaching out to us. We're here to help and happy to support you with this issue. Regarding the Published / Pending component categorization, you've actually encountered a new feature in Compass. Now, when components are imported and discovered, they go into a Pending inbox. This allows you to…

Hello, Melissa! Thank you for reaching out and sharing your experience with Compass. We understand that setting up webhooks can be a bit challenging, especially when your preferred service isn't directly supported yet. Currently, the feature to support custom webhooks is on our roadmap for Compass. Our team is actively…

That makes perfect sense, @Ana Eva Lopez . Thank you for the feedback. We have added this to our backlog.

Hi, @Ana Eva Lopez ! Thanks for pointing this out. The current setup journey checks whether the current user is part of any existing team. If you have already created all teams that you need in your Compass instance, it's true that you don't necessarily need to create a new team: you can also move forward by being added to…

Hi, @xhammer ! The Open PR metric count that you see in the component is populated based on the connection to the repository associated with that component (the repository link that you have added to the right sidebar) so that means that the data connection is successful. The pull requests tab under Teams would aggregate…

@Will Freeman if you have already upgraded your GitHub app inside of Compass to the latest version, can you log a support ticket with Atlassian, with the details of your site and what you encounter through your installation flow? That could help troubleshoot some specific problem. 

You can verify that you're using the latest version of the Compass GitHub app in your Compass instance as `https://yoursite/compass/marketplace/discover/app/compass.github` and update it if necessary. Otherwise it may be related to something specific to your configuration. If the issue persists, either sharing your site…

Hi, @Patrick Smyrl ! Currently the Compass GraphQL and the Rest APIs don't allow to directly push PR events - the documentation should be updated shortly to reflect this. Is this when you were receiving 400s? Otherwise, installing the GitHub app in Compass following these steps, and adding a repository link to your Compass…