Project Transfer Issues

[Kobby-Bawuah]

Environment

SaaS (https://sentry.io/)

Steps to Reproduce

When a project is being transferred from one org to another, there are several issues that have arisen during and after this transfer, causing problems for project access and visibility.

Upon initial analysis: It seems there may be a failure related to a bulk delete operation. This operation did not clean up some team deletions, which is likely contributing to the problems observed.

Expected Result

The project transferred from one Org to another without issues.

Actual Result

Sample situation:

Primary Org- Despite the transfer, a project will still appear in the old organization. When attempting to access it, users are greeted with a "can't be found" error message. This indicates a lingering issue with project visibility and redirection.

Secondary Org- Within the new organization, attempting to access the team's page of the transferred project results in a "something went wrong" error message. This suggests that there may be complications related to team management or project ownership.

Product Area

Settings - Projects

Link

No response

DSN

No response

Version

No response

┆Issue is synchronized with this Jira Improvement by Unito

[getsantry]

Routing to @getsentry/product-owners-settings-projects for triage ⏲️

[getsantry]

Assigning to @getsentry/support for routing ⏲️

[michaelchai-sentry]

One of our other customers just experienced the same behavior. They transferred 6 projects, the first 4 went through, and the last 2 are also experiencing the same things that Kobby described above. Would someone be able to help out with this?