David Dansby Atlassian Team

Hello Cole I'm David and I work on the Bitbucket Cloud team as a software engineer. The change could impact you depending on how you are generating those access tokens. Which OAuth 2.0 flow are you using? If you are using OAuth 2.0 Resource Owner Password Credentials Grant (4.3) to generate access tokens then this change…

Hey Chee Hwee Chai, My name is David and I'm a backend engineer on the Bitbucket Cloud team. Just to be clear, you are currently using the JWT access token in place of the OAuth access token, correct? If so, then you will not be required to make any changes. To be more specific, Bitbucket Cloud supports three of OAuth…

@Pim sorry this is happening; its a bit perplexing to me that this is happening (at least given all the information I have). Lets try a few things: * Are you able to see if any of your other colleagues have similar admin access to at least one repo with services in the same workspace and see what response they get from…

@Pim thank you for the screenshot. That is odd. I'm wondering if for some reason in that workspace your access was changed or something and you are no longer admin (this is a guess though). Can you please try running the same GET request but removing the `role=admin` URL query parameter.

@Mads K if this is for Jira Cloud, then you can no integrate Jira Cloud with Bitbucket Cloud much more easily (guide found here; please note that you a Jira admin for the Jira Cloud site you wish to integrate must give approval to the integration request). After the integration is set up you should be able to remove those…

@[deleted] yes, that is correct, for that specific repository.

hey @jamesholcomb great questions! Let me try and answer each one accordingly: * Why are Services going away?* We had originally made the push in Mid 2019 to remove the Services for webhooks but for some reason unknown to me it was never finalized. This was referenced in the very first email at the start of November 2021.…

@Pim there should be a next field in the response if you used the updated URL I provided yesterday. You would then make successive HTTP GET method calls to the URL value provided in the value of the next field. <span style="background-color: rgba(9, 30, 66, 0.08); text-align: start; text-transform:…

@cdm-atlassian The first thing you need to do is determine which repositories have Services and what those Services are based on the instructions in my original post at the top of this community page. After you determine those Services it is up to you whether you want to migrate those Services to webhooks or not. If you…

@Mads K those JIRA URLs are for a on-prem JIRA, similar to @Chris Speier 's, correct???

@Dean does the repo in question have any other admins? It could be the case that someone else you work with has already migrated the Services to a webhook and removed the Service in the Services settings page. Once all services are removed from a repository the Services settings page is no longer displayed. This was…

Sorry for the delayed response. To those only seeing responses with an empty array for Services value please read the following: Since we are filtering fields in the HTTP response via the URL query parameters, for those workspaces with 10s or 100s of repositories the fact that the URL query parameters do not include…

@Chris Speier I am a bit confused. What are the Service types/names for these two? We do not have a "jira" and a "jira pull" Service type/name. Once I know the actual Service type I can provide better information. 

@vipulpambhar that is correct. We are only asking admins that don't want to lose any specific Service functionality already enabled for a particular repository to migrate over to webhooks. We are not asking admins to disable/remove any Services they no longer wish to use and/or migrate over to webhooks. Best, David

Update 2: There have been a number of admins who have reported to us that they have existing POST and Pull Request POST Services with a URL like so https://[accountname].atlassian.net/rest/bitbucket/1.0/repository/[repo-id]/sync This is an old, carry-over from how Bitbucket Cloud used to integrate with the Jira. None of…