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

Set iteration path in calculated value

Hello, 

During de synch of defects between HPQC and AZDO I would like to set two values in the target (azdo) : 

  • When "is new" ==> set areapath to "Myproject/support/Myapp"  ==> Ok it works 
  • When 'is new' ==> set Iteration Path to "Myproject/support" (and inside this iteration path I've severals sprints) ==> It does'nt work and i reveive this error : 
  • com.connect.api.exceptions.syncLifecycle.SkipSyncItemException: failed to find itemId=Myproject/support, during iteration 2, throwing skipSyncItemException
    at com.connect.server.sync.RelationshipManager.findItemFromDataPools(RelationshipManager.java:1359)
    at com.connect.server.sync.RelationshipManager.findItemWithType(RelationshipManager.java:1192)
    at com.connect.server.sync.RelationshipManager.findItemWithType(RelationshipManager.java:1186)
    at com.connect.server.sync.ConnectorRelationshipManager.findItemWithType(ConnectorRelationshipManager.java:246)
    at com.connect.server.params.CalculatedValueEvaluator.findMatchingItem(CalculatedValueEvaluator.java:926)
    at com.connect.server.params.CalculatedValueEvaluator.setCalculatedValue(CalculatedValueEvaluator.java:815)
    at com.connect.server.sync.SyncSet.setCalculatedValues(SyncSet.java:3468)
    at com.connect.server.sync.SyncSet.addItem(SyncSet.java:2717)
    at com.connect.server.sync.SyncSet.addCorrespondingTargetItem(SyncSet.java:2769)
    at com.connect.se...

I saw that an "Iteration" can be an object (a sprint) of a String, so I tried to synchronize also iteration (with no value) to force to find the iteration but no more success. 

Someone has a suggestion to solve my problem ? 

Thanks in advance

Vianney 

  • 0

    Hi Vianny,

    You'll need to map the Iteration Path to Release Cycle, so that the relationships can be created/maintained by Connect,

    this is covered in the online help

    Use-case: Syncing ALM and Azure DevOps (microfocus.com)

    you can choose to let connect sync the iteration path to release cycles or you can do so manually & import the cross references for those you consider relevant.

    (see the match by name utilities)

    if you need help with these strategies, please open a support incident, email the case ID to me, and we'll set up a webex meeting with you.

    take care

    anil

  • 0 in reply to 

    Hello Anil, 

    Thanks for your help, finally I found a workaround without mapping release cycles with forcing in calculated value the Iteration ID and not the iteration path and it works now. 

    Vianney