Yes, you can map any type in one product to any type of your choosing in another product.
Micro Focus Connect uses the connection and data source details (servers, projects, etc.) to define the links between the corresponding items in the synchronized products. If these details are removed, the links become redundant. The next time you connect the same two products, a duplicate set of links will be created.
You can delete a data source and connection as long as they haven't been used in a synchronization.
Yes. After you create a connection, you can specify any number of combinations of projects between the data sources. The only condition is that the paired projects need to conform to the data source restrictions. For example, AzureDevOps requires that paired projects are of the same project type.
Yes, the data sources describe how to connect to a server. The connection then uses the data source to describe how to map types and projects within that data source.
You cannot use the same data source for both sides of the connection. If you want to synchronize between projects within the same product, you can create a second data source with the same server details, and use the two data sources at either side of a connection.
Micro Focus Connect uses several levels of information in the products to detect changes, and to determine which side made a change most recently. In the rare case where this information is insufficient to determine which side's changes should be applied, Micro Focus Connect resorts to the master. Most products nowadays provide sufficient details, making this designation almost redundant.
Yes. Micro Focus Connect surfaces the relationships as fields in the mapping for a type in a connection, you choose the relationship field in one product and then choose the relationship in the other product that you want to use to represent this relationship.
Yes, depending on the product. For example, Rally understands and describes when a Story has moved from one project to another.
No. Most products do not support changes in types. Micro Focus Connect will create a parallel item in the new type, provided the new type is configured in a Connection.
Yes. Any failure to synchronize an item is tracked and recorded. Micro Focus Connect will retry twice. If it continues to fail, it will stop trying. After this point, if Micro Focus Connect detects a change to the item (for example, if you fixed a bad status value) it will try synchronizing again. Finally, if you clear the watermarks for a connection, this also clears the failure state on items, and Micro Focus Connect will resume its attempts to synchronize.
In some systems, such as ALM Octane and Jira, images embedded in memo fields are saved as attachments. In other systems, such as Azure DevOps, embedded images are not saved as attachments.
When an Azure DevOps item with an embedded image is synchronized with ALM Octane, for example, the image is saved in ALM Octane as an attachment. The attachment from ALM Octane is then synchronized back to Azure DevOps and appended to the original item as an attachment. Both of these operations are completed within the same connection iteration.
Note: This behavior relates to Micro Focus Connect 4.4.1 and higher.