How can we handle when issue is moved between one project to another?

Originally asked by Samip K Banker on 30 August 2019 (original question)


We have a connection setup to sync Project A issue to Project B… now issue in Project A (that is already synced with Project B) is moved to Project C… and we don’t have connection setup for Project C… how do we handle this use case?


Answer by Francis Martens (Exalate) on 30 August 2019

The relation between issues is traced using the issueids. Whenever an issue is moved from Project A to Project C, the issue id remain the same - the synchronization will continue as before


Comments:

Samip K Banker commented on 30 August 2019

Ok. Thanks. Let me make usre that is behaviour we are seeing.

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.