Cross project area/iteration reference in workitem

[Lokeshmaxi]

Cross project area/iteration reference in workitem:

1. I was migrating one ADO to another ADO , with source and target has different project name. when i ran nodestructure , it is migrated all area/iteration from source to target under new project name, then when running workitemmigrationprocessor, i found some workitem referencing cross project area/iteration which i have to create those missing areas/iteration, i have used again nodestructure to map missing area/iteration for target projectname, but while creating of those missing cross project area/iteration paths, it is also tried to create actual source project area/iteration under cross project name, how to handle cross project area/iteration during migration ?

2. how to skip area/iteration validation in version 16.0.2? i want feature where to skipcheckingallarea/iteration in source history, if set to true, migration need to continue if there is missing area/iteration,this feature could be helpful for case, where workitem initally created in different project name as area/iteration and then changed into current source project name area/iteration, This attribute is not working if set to false in "StopMigrationOnMissingAreaIterationNodes": false,

3. Also how to skip history checking for workitem where initally workitem is created as Bug, then later changed to Task, During migration, these workitems throws "Error workitem is either renamed or deleted", i want to migrate only current workitem type "Bug" and skip the history of original type for workitems in source history.

[MrHinsh]

I was migrating one ADO to another ADO , with source and target has different project name. when i ran nodestructure , it is migrated all area/iteration from source to target under new project name, then when running workitemmigrationprocessor, i found some workitem referencing cross project area/iteration which i have to create those missing areas/iteration, i have used again nodestructure to map missing area/iteration for target projectname, but while creating of those missing cross project area/iteration paths, it is also tried to create actual source project area/iteration under cross project name, how to handle cross project area/iteration during migration ?

Sorry I don't understand what the issue that you are having is.

how to skip area/iteration validation in version 16.0.2? i want feature where to skipcheckingallarea/iteration in source history, if set to true, migration need to continue if there is missing area/iteration,this feature could be helpful for case, where workitem initally created in different project name as area/iteration and then changed into current source project name area/iteration, This attribute is not working if set to false in "StopMigrationOnMissingAreaIterationNodes": false,

StopMigrationOnMissingAreaIterationNodes is not a valid option. There is ShouldCreateMissingRevisionPaths and ReplicateAllExistingNodes options only. see https://devopsmigration.io/docs/reference/tools/tfs-node-structure-tool/

Also how to skip history checking for workitem where initally workitem is created as Bug, then later changed to Task, During migration, these workitems throws "Error workitem is either renamed or deleted", i want to migrate only current workitem type "Bug" and skip the history of original type for workitems in source history.

"Error workitem is either renamed or deleted" is not due to a work item having its type changed. I think its due to the Work Item Type being missing. Do you have them all mapped? See https://devopsmigration.io/docs/reference/tools/work-item-type-mapping-tool/