This is disastrous. Every existing "hook" I have setup under "Services" which are just standard POST calls have to be changed to be another form of webhook? There was no way to migrate this over or build a tool, you just put this on your customers with this extremely poorly explained email and support page? @David Dansby this is horrible and seriously making me consider continuing being a bitbucket/atlassian customer.
We're being asked to do atlassian's work for them and I don't appreciate it. Our webhooks are functioning just fine, if you want them in another format for your back end then it is a tool that your organization should provide or migrate internally. If required to touch every repository, I will go ahead and move them elsewhere at the same time.
Atlassian Team members are employees working across the company in a wide variety of roles.
December 8, 2021 edited
@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 2 Services.
Atlassian Team members are employees working across the company in a wide variety of roles.
December 8, 2021 edited
@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.
@David Dansby Thanks for troubleshooting with me. Removing the `role=admin` URL query parameter does not yield a different result.
I've reviewed my access to the repositories in the workspace. For all 443 repos I have admin access through the 'Administrators' user group. When reviewing access rights I noticed I additionally have 'Direct access' to a subset of 7 repositories.
I've tried lowering the `pagelen` URL query parameter below 7 (with/without `role=admin`), but go no change in the responses. I've tried creating another app password for API authorization with full rights (with/without `role=admin`), but got no change in the responses.
Atlassian Team members are employees working across the company in a wide variety of roles.
December 10, 2021 edited
@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 running the same API engpoint?
Can you please try running the same API call via cURL? example (please change <username> and <password> accordingly. Note, password should be app password you just made)
Apologies that the API call didn't return any data for you. I'm going to reach out to you directly on the ticket and share with you the list of repositories that are going to be affected by this deprecation.
We have few repositories with Services enabled, if we decide not to use services feature in those repositories, does that effect anything to that repositories ? Is there any remedies that we've to take to avoid? Is there a backups of that ? Thank you!
Leaving Services until we remove them for you will not affect anything for your and your team.
Those will be removed automatically by our team and all integrations that are using Services will stop working as of December 31.
For any integration you would like to add or make sure that the integration continues to work after the deprecation, please switch over to webhooks based integration, as described by David.
We will not be creating a backup for anything that is getting removed at the end of this month.
Thank you for confirming, we have removed all the services POST urls, since we no longer need them. Just to make sure, when Services feature removed, this is not going to impact any of our existing repositories right ?
38 comments