narrowizard opened a new issue, #6336: URL: https://github.com/apache/incubator-devlake/issues/6336
### Search before asking - [X] I had searched in the [issues](https://github.com/apache/incubator-devlake/issues?q=is%3Aissue) and found no similar issues. ### What happened During the process of synchronizing TAPD data, I noticed an issue in the domain layer. There was a cross-connection reference where an issue from connection 12 was referring to a sprint from connection 4. This occurred in the 'issue_changelogs' table in the domain layer. This breach in data isolation between different connections might affect data integrity and accuracy. ### What do you expect to happen The data should be isolated and contained within their respective connections during synchronization. An issue from one connection shouldn't reference the sprint from another connection. Therefore, connection 12 data should only reference other data from the same connection and not from connection 4. The integrity of segregated data should be maintained. ### How to reproduce 1. create multi connections with the same tapd source(endpoint, username, password) 2. Start the TAPD data synchronization process in DevLake for the same workspaces on different connections. 3. Monitor the data in the domain layer and specifically look at the 'issue_changelogs' table. 4. Identify if there are any cross-connections, where data from one connection is referring to data from another connection. ### Anything else  ### Version release-v0.19 ### Are you willing to submit PR? - [ ] Yes I am willing to submit a PR! ### Code of Conduct - [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
