Reminder: “List pull requests for a user” API removal

[#1]

Hi Bitbucket community,

This is a reminder about a Bitbucket Cloud REST API endpoint that will be removed on Feb 20, 2025. If you’re currently making calls to this endpoint, you’ll need to make changes ASAP. Please continue reading to understand how you may be impacted.

What is changing

As mentioned in a previous deprecation notice, on Feb 20, 2025 Bitbucket will be removing the List pull requests for a user API endpoint, which fetches pull requests authored by a given user across all of their workspaces.

We have introduced a new endpoint, List workspace pull requests for a user, which limits results to a single workspace. This new operation works the same way as the deprecated endpoint but requires the {workspace} path parameter.

Note: If you need to retrieve pull requests authored by a given user across multiple workspaces, follow these steps:

1. Get the list of available workspaces using the List workspaces for user operation.
2. Iterate over the list of workspaces and use the List workspace pull requests for a user operation to get requests authored by the user in each workspace.

Who this impacts

• REST API users - If you’ve written an application or automation that calls the deprecated endpoint, you should migrate to the new endpoint ASAP. The deprecated endpoint will return a 404 error starting on Feb 20, 2025.
• GitKraken Desktop users - If you’re using GitKraken Desktop with Bitbucket Cloud repos, you should update to version 10.6.3 or later. Previous versions were making use of the deprecated endpoint, and will stop working correctly as of Feb 20, 2025.

Timing

The List pull requests for a user endpoint will be removed on Feb 20, 2025. You should plan to migrate your usage before then.

[Danny Yu]

The pop-up alert in my PR startled me significantly

[Purwanto]

you can hide it with click the `dismiss` button @Danny Yu 

[Prashant Gouda]

Why the yellow alert popup is showing, and what it the new change??

[Eben]

@Prashant Gouda To alert users of the removal of an endpoint to list PRs for a user.
You can read the article above for full context.

[UTKARSH]

Can anyone actually elaborate about this new change which's gonna happen in clear simple interpretable words. Any effect on merging PR, raising PR, querying through different states of PR like 'Merged', 'Open', 'Declined'? Or, any changes in querying through adding relevant author, target branch, etc?

Waiting for a simple explanation - advantages/disadvantages

[Milan Kacar]

Am I going to be affected by that? I am using bitbucket from Looker and in Dataform.

[Gerard McHale]

We are using the endpoint

2.0/repositories/$BITBUCKET_WORKSPACE/$BITBUCKET_REPO_SLUG/commit/$BITBUCKET_COMMIT/pullrequests

 in our pipelines. Will the deprecation of the endpoint below affect the above endpoint call?

2.0/pullrequests/{selected_user}

[Alex Harper]

It's all very good and well listing your previous deprecation notice in this post, but I only started to get the yellow popup today. So 9 days notice to update our tooling, when I will be out of office from tomorrow. Not acceptable!

[Dave Parrish _Atlassian_]

Hi all 👋 This change will have zero impact on day-to-day usage of Bitbucket via the UI, nor on any other REST endpoints. Most customers won't need to do anything. But if you've got an application that happens to call the deprecated endpoint, you'll need to update your usage.

[Tom Gagne]

I'm unclear how the new endpoint will support listing PRs for a specific repo.

[Dave Parrish _Atlassian_]

Hi @Tom Gagne 👋

The repository-level pull requests endpoint (/repositories/{workspace}/{repo_slug}/pullrequests) is not impacted by this change. You can continue using it to fetch PRs for a given repository.