How to avoid Exalate from creating new issues after the issue has been unexalated

General Questions
, ,
1

Originally asked by Harold Oconitrillo on 24 November 2022 (original question)

Hi,

I try to use syncHelper.isIssueUnderSync in the out sync to avoid Exalate from creating new issues after the issue has been unexalated, but the helper function seems to always return false irrespective of the issue being in sync or not.

I have attached the support zip for reference. Please let us know if there is a workaround for this or better way to make sure once the issue is unexalated, it cannot Exalate again when updates are made to it.

Any insight is much appreciated.

Thank you,