This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

How to handle the synchronization of links for partial synchronized objects / non-sychronized linking partners

General Question that can appear in a lot of different situations on synchronization:

In one system you have objects which are synchronized to another system.

These objects have links to other objects, and the linking information should also be synchronized.

As long as the object and all linked objects are synchronized, the linking can also be synchronized.

But as soon as a linked object is not synchronized the attempt to synchronize the linking runs into an failure. 

What is needed here is somekind of "graceful ignorance" - if a link can not be created during the synchronisation of an object, because the linked object dosesn't exist in the target system, than this should be ignored (or siliently logged as a warning, not treated as an error.

Is there anyway to do this or another solution for this kind of situations?

Example situations, were this problem appears:

1.) Some Jira Issues with their relations are synchronized to MF ALM Defects and links between Defects. However, as soon as a synchronized Jira Issue has a relation with an unsynchronized Jira Issue, the synchronization will run into an error.

2.) Tests and Defects and their linking are synchronized from MF ALM to Jira. But not all Tests are synchronized to Jira only a subset, and as soon as a Defect is linked to a not synchronized Test, the synchronization will run into an error

3.) Test, Requirements and their linking is synchronized between MF ALM and MF Dimensions. But as soon as an Requirement in MF ALM is linked to a Test in MF ALM which is not synchronized to MF Dimensions, the synchronization will run into an error

  • 0

    Note: This is more than a nuisance: If the synchronization fails due to this, also all other changes on the affected object will not be synchronized.

  • Verified Answer

    +1 in reply to 

    Good morning, yes, this is, unfortunately, a side effect of the architecture.

    No, there is no Connect workaround for it, other than ignoring the relationships.

    However, if the links(relationships) themselves are synced uni-directionally - 

    from jira to alm/qc, from alm/qc to jira,

    & if you'd like to raise an incident, email me the incident number, and request escalation to cfrd,

    then I may be able to come up with a workaround. (i make no guarantees), specifically for jira to/from alm/qc.

    if the link synchronization is bi-directional, &/or dimensions is involved, then I have no workarounds.

  • 0 in reply to 

    Thanks for the fast & honest answer.

    For my specific usecase, I removed all relationships/linking from the synchronization scope.

    However this is also a relevant limitation for other projects in my company, so I asked the responsible colleague to request a change in MF Conect for this.