hi Jillani,
I am referring to closed Zendesk tickets linked 100s or 1000s of closed Jira issues.
thanks, Sandra
Thank you for the update.
The number of tickets does impact on the performance if the trigger is involved. Also, if you do not want these issues to be counted under the sync process after they are closed, you can either use the Unexalate post function or Bulk Unexalate operation.
Here are the articles:
https://docs.exalate.com/docs/exalate-now-post-function (this is actually for Exalate function but the steps are the same for Unexalate Post Function)
https://docs.exalate.com/docs/bulk-unexalate
I hope that you will find the shared solution helpful.
Regards,
Jillani
Thank you for connecting with us.
May I know if you are referring to open issues when mentioning "100's or 1000's sync'd connections left active between Zendesk and Jira"?
hello,
We have multiple (currently 6) scripted connections between Zendesk and Jira OnPrem with a many to many configuration. ie. a Zendesk ticket can have multiple connections to Jira projects and a Jira issue can have multiple connections to a Zendesk ticket.
If we do not unexalate these connections we would potentially have 100's or 1000's sync'd connections left active between Zendesk and Jira. Is there a limit to the number of active sync'd connections we can leave open? Could there be an impact on performance if we do not periodically clean-up? Can you provide any more information about the effect of many active connections?
thanks, Sandra