Support moving of issues between two synchronizations
Description
Following setup: A user is synchronizing project A with B and A with C. If he moves an issue from B to C, Backbone will create a new issue in A even if the issue was synced before from B to A, because Backbone detects this as a change in the project C.
Suggested Improvement
We should identify if an issue has been moved between two projects if both projects are part of a Backbone sync. One option would be to show this conflict in the troubleshooting section and provide an action to let the user decide how to continue, i.e. create a new issue or continue to sync with an existing one. In case the issue was synced with >1 other issues, we should provide a list of potential target issues.
Following setup: A user is synchronizing project A with B and A with C. If he moves an issue from B to C, Backbone will create a new issue in A even if the issue was synced before from B to A, because Backbone detects this as a change in the project C.
Suggested Improvement
We should identify if an issue has been moved between two projects if both projects are part of a Backbone sync. One option would be to show this conflict in the troubleshooting section and provide an action to let the user decide how to continue, i.e. create a new issue or continue to sync with an existing one. In case the issue was synced with >1 other issues, we should provide a list of potential target issues.