[Bug]: TfsSharedQueryProcessor doesn't migrate area selection where @CurrentIteration is used

[lukelloydagi]

Version

• I confirm that I am using the latest version

Source Version

Azure DevOps Service

Target Version

Azure DevOps Service

Relevant configuration

{
  "Serilog": {
    "MinimumLevel": "Information"
  },
  "MigrationTools": {
    "Version": "16.0",
    "Endpoints": {
      "Source": {
        "EndpointType": "TfsEndpoint",
        "Collection": "https://dev.azure.com/{source}/",
        "Project": "{project}",
        "Authentication": {
          "AuthenticationMode": "AccessToken",
          "AccessToken": "*****"
        }
      },
      "Target": {
        "EndpointType": "TfsEndpoint",
        "Collection": "https://dev.azure.com/{target}/",
        "Project": "{project}",
        "Authentication": {
          "AuthenticationMode": "AccessToken",
          "AccessToken": "*****"
        }
      }
    },
    "Processors": [{
        "ProcessorType": "TfsSharedQueryProcessor",
        "Enabled": true,
        "SourceName": "Source",
        "TargetName": "Target"
      }
    ]
  }
}

Relevant log output

What happened?

Queries get migrated without any warnings or errors, however they are missing the area selection where @CurrentIteration is used:

Debug in Visual Studio

• Visual Studio Debug

[MrHinsh]

Yup, I dont think the Tfs Object Model supports this.