"FilterWorkItemsThatAlreadyExistInTarget" and "Maps" Bug found, I think

[stevns]

Hello Dear Azure DevOps Migrators,

I think I found a bug in the "AreaMaps" and "IterationMaps" in relation to the checking of already migrated workitems rutine.

If you are have the "FilterWorkItemsThatAlreadyExistInTarget" set to true, this does not correctly run this through the maps that are done for Area and Iterations, which then gifts you with the lovely error:

Microsoft.TeamFoundation.WorkItemTracking.Client.ValidationException: TF51011: The specified iteration path does not exist. The error is caused by «'migtest\S1\S1.1CPQ\Sprint wk17-18 2022'».

Seems that it concatenates the original path (CPQ\Sprint wk17-18 2022) on the back of the new target path (migtest\S1\S1.1).

UPDATE: This also affects "ReplayRevisions" :-/

If this is an ID10T error, please advise :)

Cheers

Martin

[MrHinsh]

Correct. At this time only the project change is reflected in 'FilterWorkItemsThatAlreadyExistInTarget', and we do not use any Area or Iteration Mappings. To avoid this issue we recommend that you use the same area & iteration paths in the source and the target until you have completed the migration. Or use the AppendProjectName option to create a set of easily deleted sub-areas. But I can see how this would not work if you map the area or iteration paths.

We are always open to pull requests.

[NormanGarciaV]

Hi,
This conversation is quite old.. but.. having kind of the same issue. So wonder if you guys can help.
Ran some migrations when the query was to migrate all with version 15.0. No problems there. Migrating from Az DevOps to Az DevOps.

Now, using v15.1, as the source has thousands of items... I filtered the query based on an area path, but it errors (see below).

The area path is complaining about, exists in the source, so thought the area did not exist in the target, so I created the team and the area associated to it, but did not help.

[09:30:48 INF] [15.1.6] [FilterWorkItemsThatAlreadyExistInTarget] is enabled. Source project RBS Portfolio is replaced with target project EVR Applications Portfolio on the WIQLQuery which resulted into this target WIQLQueryBit "SELECT [System.Id], [System.WorkItemType], [System.Title], [System.AssignedTo], [System.State], [System.AreaPath], [System.CreatedDate] FROM workitems WHERE [System.TeamProject] = 'EVR Applications Portfolio' AND [System.CreatedDate] > '2024-07-30' AND [System.AreaPath] UNDER 'EVR Applications Portfolio\Practices\Integration\RT-Horizon'" .
[09:30:48 DBG] [15.1.6] FilterExistingWorkItems: START |
[09:30:48 DBG] [15.1.6] FilterByTarget: Query Execute...
[09:30:48 DBG] [15.1.6] WorkItemQuery: ===========GetWorkItems=============
[09:30:48 DBG] [15.1.6] WorkItemQuery: TeamProjectCollection: https://dev.azure.com/elkvalleyresources/
[09:30:48 DBG] [15.1.6] WorkItemQuery: Query: SELECT [System.Id], [System.WorkItemType], [System.Title], [System.AssignedTo], [System.State], [System.AreaPath], [System.CreatedDate] FROM workitems WHERE [System.TeamProject] = 'RBS Portfolio' AND [System.CreatedDate] > '2024-07-30' AND [System.AreaPath] UNDER 'RBS Portfolio\Practices\Integration\RT-Horizon'
[09:30:48 DBG] [15.1.6] WorkItemQuery: Parameters: {"TeamProject": "EVR Applications Portfolio", "ReflectedWorkItemIdFieldName": "Custom.ReflectedWorkItemId"}
[09:30:48 DBG] [15.1.6] WorkItemQuery: TeamProject: EVR Applications Portfolio
[09:30:48 DBG] [15.1.6] WorkItemQuery: ReflectedWorkItemIdFieldName: Custom.ReflectedWorkItemId
[09:30:48 DBG] [15.1.6] Query sent
[09:30:48 ERR] [15.1.6] Error running query
Microsoft.TeamFoundation.WorkItemTracking.Client.ValidationException: TF51011: The specified area path does not exist. The error is caused by «'RBS Portfolio\Practices\Integration\RT-Horizon'».
at Microsoft.TeamFoundation.WorkItemTracking.Client.Query.Initialize(WorkItemStore store, String wiql, IDictionary context, Int32[] ids, Int32[] revs, Boolean dayPrecision)
at Microsoft.TeamFoundation.WorkItemTracking.Client.WorkItemStore.Query(String wiql, IDictionary context)
at MigrationTools._EngineV1.Clients.TfsWorkItemQuery.GetWorkItemsFromQuery(TfsWorkItemMigrationClient wiClient) in D:\a\azure-devops-migration-tools\azure-devops-migration-tools\src\MigrationTools.Clients.AzureDevops.ObjectModel_EngineV1\Clients\TfsWorkItemQuery.cs:line 53

Any thoughts??

Thanks.
Norman.

[MrHinsh]

Yup, using a WIQL with content specific to the source generally is incompatible with FilterWorkItemsThatAlreadyExistInTarget.

However, I can see that the Acutall query run is not the updated one above. It will need investigation.

[MrHinsh]

Yup! Fix inbound! #2233

Will be in https://github.com/nkdAgility/azure-devops-migration-tools/releases/tag/v15.1.7-Preview.5 once it releases... give it 12m for the PR, and then 12m for the preview release!

[NormanGarciaV]

Thanks a lot @MrHinsh