500 Internal Server Error when declining/cancelling new PRs after workspace migration

[Tarunkumar]

We recently migrated our repositories from one Bitbucket workspace to another. Since then, whenever I try to decline or cancel a pull request, Bitbucket shows a 500 Internal Server Error.

• I have full admin access to both the repository and project.

• This only happens with new PRs created after the migration.

• I’ve tried different browsers, clearing cache, and checking permissions/branch restrictions, but the issue persists.

Has anyone experienced this before?

• Could it be related to stale PR metadata after the migration?

• Do we need Atlassian support to refresh/reindex something at the workspace level?

• Are there additional settings required for declining PRs after migrating a repo?

Any suggestions or workarounds would be really helpful.

Thanks in advance!

[Syahrul]

Hey @Tarunkumar 

Welcome to the community!

Could you please raise a support ticket on our Support portal so we can help investigate the issue further?

Thanks!
Syahrul