Project transfer does not transfer environments correctly
- Dominant language
- Python
- Stars
- 44.8k
- Forks
- 4.9k
- Avg merge
- 22h 21m
- Merged PRs (30d)
- 586
Description
### Environment
SaaS ([https://sentry.io/]())
### Steps to Reproduce
1. Have a project with an error event (issue A) from a specific environment, ie. `production`
Transfer the project to another Sentry organization
1. Using the new DSN, send a new type of error (issue B) to the `production` environment
2. Filter your Issue page results by the `production` environment
### Expected Result
Both issue A and issue B are visible when applying this filter.
### Actual Result
Only issue B is visible when applying this filter.
Video reproduction from my test org where ZeroDivisionError happened before the project transfer, and KeyError happened after the project transfer:
https://github.com/user-attachments/assets/0da5deca-b3c6-4d0b-80e6-dd9f3e56579e
The test project is [here]() and was transferred from my other test org `dragonfruit-us`.
### Product Area
Issues
### Link
*No response*
### DSN
*No response*
### Version
*No response*
Contributor guide
Assessment
This issue has not been assessed yet.