We have noticed a discrepancy in MFConnect, when we sync with Octane. When syncing data between Octane and Azure DevOps the Close date is actual -1 in the past, has anyone seen this?

We are using MF connect to synchronize defects between azure dev ops and ALM octane we have noticed that tags do not seem to sync properly with some of them getting lost when syncing back and forth, has anyone else noticed this?

Using MF Connect version 4.3.1, it seems to be consuming alot of memory and connections with ALM octane.

We are using MF Connect 4.3.1 and we are synchronizing comments back and forth between AZDO and Octane. We have run into a weird issue where when we create a new comment in an azure ticket it is created as a new entity in Octane essentially making a duplicate issue in octane.