RefectedWorkItemId field value cannot be null #2391

Nikkath15 · 2024-09-24T00:08:02Z

Nikkath15
Sep 24, 2024

Hello Team,

I am attempting to migrate an ADO board hosted on an internal network (GIDE ADO) to an external ADO board using devops migration tools. However, I am encountering an error message.

Could you please assist me in understanding the error message? I also wanted to confirm if it is necessary to add the ReflectedWorkItemIdField in both the source and target systems. I have already added this field in the target system for the 'User Story' work item type, as i am trying to testing only "user story' for now.

I have also
configuration_sample.txt
attached my configuration.json file for the reference.

16:19:18 DBG] [16.0.1] ===================================
[16:19:18 DBG] [16.0.1] Configuring 'MigrationTools:Processors:0:Enrichers'
[16:19:18 DBG] [16.0.1] ===================================
[16:19:18 INF] [16.0.1] Creating Migration Engine dd079216-cfb1-4894-95c6-23d214848ed5
[16:19:18 INF] [16.0.1] ProcessorContainer: Of 1 configured Processors only 1 are enabled
[16:19:18 INF] [16.0.1] ProcessorContainer: Adding Processor TfsWorkItemMigrationProcessor
[16:19:18 DBG] [16.0.1] Constructor found: IOptions`1, TfsCommonTools, ProcessorEnricherContainer, IServiceProvider, ITelemetryLogger, ILogger`1
[16:19:18 DBG] [16.0.1] Attempting to pass parameters: OptionsWrapper`1
[16:19:18 DBG] [16.0.1] ===================================
[16:19:18 DBG] [16.0.1] Configuring 'MigrationTools:CommonTools:FieldMappingTool:FieldMaps'
[16:19:18 DBG] [16.0.1] Configuring '0' as 'IFieldMapOptions' from 'MigrationTools:CommonTools:FieldMappingTool:FieldMaps'
[16:19:18 DBG] [16.0.1] Configuring '1' as 'IFieldMapOptions' from 'MigrationTools:CommonTools:FieldMappingTool:FieldMaps'
[16:19:18 DBG] [16.0.1] ===================================
[16:19:18 INF] [16.0.1] FieldMappingTool: Adding FieldMap FieldToFieldMap for User Story
[16:19:18 INF] [16.0.1] FieldMappingTool: Adding FieldMap FieldToFieldMap for User Story
[16:19:18 INF] [16.0.1] Logging has been configured and is set to: unknown.
[16:19:18 INF] [16.0.1]                               Max Logfile: Verbose.
[16:19:18 INF] [16.0.1]                               Max Console: Debug.
[16:19:18 INF] [16.0.1]                  Max Application Insights: Error.
[16:19:18 INF] [16.0.1] The Max log levels above show where to go look for extra info. e.g. Even if you set the log level to Verbose you will only see that info in the Log File, however everything up to Debug will be in the Console.
[16:19:18 INF] [16.0.1] Beginning run of 1 processors
[16:19:18 INF] [16.0.1] Processor: TfsWorkItemMigrationProcessor
[16:19:18 INF] [16.0.1] Migration Context Start: TfsWorkItemMigrationProcessor
[16:19:18 DBG] [16.0.1] WorkItemMigrationContext::InternalExecute
[16:19:18 WRN] [16.0.1] TfsNodeStructureTool: TfsNodeStructureTool is disabled! This may cause work item migration errors!
[16:19:18 INF] [16.0.1] ----------------------------------------------
[16:19:18 INF] [16.0.1] Migrating all Teams before the Processor run.
[16:19:18 DBG] [16.0.1] TfsMigrationClient::GetDependantTfsCollection:AuthenticationMode(AccessToken)
[16:19:18 INF] [16.0.1] Connecting with AccessToken
[16:19:18 DBG] [16.0.1] MigrationClient: Connecting to https://xxx
[16:19:20 INF] [16.0.1] Access granted to https://xxx for 
[16:19:20 DBG] [16.0.1] TfsMigrationClient::GetDependantTfsCollection:AuthenticationMode(AccessToken)
[16:19:20 INF] [16.0.1] Connecting with AccessToken
[16:19:20 DBG] [16.0.1] MigrationClient: Connecting to https://xxx
[16:19:20 INF] [16.0.1] Access granted to https://xxx for 
[16:19:20 INF] [16.0.1] TfsTeamSettingsProcessor::InternalExecute: Found 1 teams in Source?
[16:19:21 DBG] [16.0.1] Found 1 teams in Target?
[16:19:21 DBG] [16.0.1] DONE in 00:00:00.4631947
[16:19:21 INF] [16.0.1] Querying items to be migrated: SELECT [System.Id] FROM WorkItems WHERE [System.TeamProject] = @TeamProject AND [System.WorkItemType] NOT IN ('Test Suite', 'Test Plan','Shared Steps','Shared Parameter','Feedback Request') ORDER BY [System.ChangedDate] desc ...
[16:19:21 DBG] [16.0.1] WorkItemQuery: ===========GetWorkItems=============
Initializing expensive WorkItemStore...
[16:19:21 DBG] [16.0.1] TfsWorkItemMigrationClient::GetWorkItemStore(https://xxx, BypassRules)
[16:19:22 INF] [16.0.1] Work Item Store connected to https://xxxx/ with BypassRules set to True
[16:19:22 DBG] [16.0.1] WorkItemQuery: TeamProjectCollection: https://xxxx
[16:19:22 DBG] [16.0.1] WorkItemQuery: Query: SELECT [System.Id] FROM WorkItems WHERE [System.TeamProject] = 'xxxx' AND [System.WorkItemType] NOT IN ('Test Suite', 'Test Plan','Shared Steps','Shared Parameter','Feedback Request') ORDER BY [System.ChangedDate] desc
[16:19:22 DBG] [16.0.1] WorkItemQuery: Parameters: {"TeamProject": "xxxx", "ReflectedWorkItemIdField": null}
[16:19:22 DBG] [16.0.1] WorkItemQuery: TeamProject: xxxx
[16:19:22 DBG] [16.0.1] WorkItemQuery: ReflectedWorkItemIdField: null
[16:19:22 DBG] [16.0.1] Query sent
[16:19:23 INF] [16.0.1] 759 Work items received, verifying
[16:19:28 INF] [16.0.1] Loading 759 Work Items
[16:19:58 INF] [16.0.1] 24/759 3.16%
[16:20:29 INF] [16.0.1] 112/759 14.76%
[16:20:59 INF] [16.0.1] 173/759 22.79%
[16:21:29 INF] [16.0.1] 245/759 32.28%
[16:21:59 INF] [16.0.1] 308/759 40.58%
[16:22:30 INF] [16.0.1] 381/759 50.2%
[16:23:00 INF] [16.0.1] 454/759 59.82%
[16:23:30 INF] [16.0.1] 530/759 69.83%
[16:24:00 INF] [16.0.1] 607/759 79.97%
[16:24:31 INF] [16.0.1] 674/759 88.8%
[16:25:01 INF] [16.0.1] 741/759 97.63%
[16:25:10 DBG] [16.0.1] 759 Work Items loaded
[16:25:10 INF] [16.0.1] Replay all revisions of 759 work items?
[16:25:10 INF] [16.0.1] Validating::Check all Target Work Items have the RefectedWorkItemId field
Initializing expensive ProjectData from WorkItemStore...
Initializing expensive WorkItemStore...
[16:25:10 DBG] [16.0.1] TfsWorkItemMigrationClient::GetWorkItemStore(https://dev.azure.com/xxxx/, BypassRules)
[16:25:22 INF] [16.0.1] Work Item Store connected to https://dev.azure.com/xxxx/ with BypassRules set to True
Error logged to Elmah.io!
!! Check for latest version - We fix issues constantly - If not, please create a discussion on https://github.com/nkdAgility/azure-devops-migration-tools/discussions so we can get this fixed !!
[16:25:24 FTL] [16.0.1] Error while running TfsWorkItemMigrationProcessor
System.ArgumentNullException: Value cannot be null.
Parameter name: name
   at Microsoft.TeamFoundation.WorkItemTracking.Client.FieldDefinitionCollection.Contains(String name)
   at MigrationTools.Tools.TfsValidateRequiredFieldTool.ValidatingRequiredField(TfsProcessor processor, String fieldToFind, List`1 sourceWorkItems) in D:\a\azure-devops-migration-tools\azure-devops-migration-tools\src\MigrationTools.Clients.TfsObjectModel\Tools\TfsValidateRequiredFieldTool.cs:line 47
   at MigrationTools.Processors.TfsWorkItemMigrationProcessor.ValidateAllWorkItemTypesHaveReflectedWorkItemIdField(List`1 sourceWorkItems) in D:\a\azure-devops-migration-tools\azure-devops-migration-tools\src\MigrationTools.Clients.TfsObjectModel\Processors\TfsWorkItemMigrationProcessor.cs:line 269
   at MigrationTools.Processors.TfsWorkItemMigrationProcessor.InternalExecute() in D:\a\azure-devops-migration-tools\azure-devops-migration-tools\src\MigrationTools.Clients.TfsObjectModel\Processors\TfsWorkItemMigrationProcessor.cs:line 128
   at MigrationTools.Processors.Infrastructure.Processor.Execute() in D:\a\azure-devops-migration-tools\azure-devops-migration-tools\src\MigrationTools\Processors\Infrastructure\Processor.cs:line 105
[16:25:24 INF] [16.0.1] TfsWorkItemMigrationProcessor completed in 00:00:00
[16:25:24 ERR] [16.0.1] TfsWorkItemMigrationProcessor The Processor MigrationEngine entered the failed state...stopping run
[16:25:24 INF] [16.0.1] Command ExecuteMigrationCommand completed in 00:06:06.7477505

Answered by MrHinsh

Sep 24, 2024

in your config you have ReflectedWorkItemIdFieldName instead of ReflectedWorkItemIdField. This leaves the field empty as there is no default.

This is validated in newer versions.

View full answer

2024-09-24T07:58:08Z

nkdagility-actions-bot[bot]
bot Sep 24, 2024

Hi there,

You're reporting a problem with an old version of the Azure DevOps Migration Tools. Please try the latest version and tell us if that fixes your problem. Bonus points for also trying with the latest preview version.

Good luck,

Thanks, Azure DevOps Migration Tools team

0 replies

MrHinsh · 2024-09-24T11:01:07Z

MrHinsh
Sep 24, 2024
Maintainer

in your config you have ReflectedWorkItemIdFieldName instead of ReflectedWorkItemIdField. This leaves the field empty as there is no default.

This is validated in newer versions.

0 replies

Nikkath15 · 2024-09-25T18:45:41Z

Nikkath15
Sep 25, 2024
Author

Hello Team,

I have tried with the latest version as well as preview version , both ended up in below error. I have used the attached configuration file. Even though I have mentioned PAT token details under access token , getting error as
[11:40:31 FTL] [16.0.3] Validation of your configuration failed:
The configuration entry at 'MigrationTools:Endpoints:Target2' did not pass validation!
Please check the following failures:
-The AccessToken must not be null or empty when AuthenticationMode is set to 'AccessToken'.

Ouput logs:

C:\Users\workspace\DevopsMigrationtool>devopsmigration execute --config configuration.json --dry-run
_ ____ ___
/ \ ____ _ _ _ __ ___ | _ \ ___ __ __ / _ \ _ __ ___
/ _ \ |_ / | | | | | '| / _ \ | | | | / _ \ \ \ / / | | | | | '_ \ / |
/ ___ \ / / | || | | | | __/ | || | | / \ V / | || | | |) | __
// _\ /| _,| |_| _| |____/ _| _/ _/ | ./ |__/
||

| / | () __ _ _ __ __ _ | | () ___ _ __ | | ___ ___ | | ___
| |/| | | | / | | '__| / _ | | _| | | / _ \ | ' \ | | / _ \ / _ \ | | / __|
| | | | | | | (| | | | | (| | | |_ | | | () | | | | | | | | () | | () | | | _
|| || || _, | || _,| _| || ___/ || || || _/ _/ || |/
|/
[11:40:29 INF] [16.0.3] Azure DevOps Migration Tools [Object Model]
[11:40:29 INF] [16.0.3] 16.0.3
[11:40:29 INF] [16.0.3] naked Agility with Martin Hinshelwood
[11:40:29 INF] [16.0.3] ===============================================================================
[11:40:29 INF] [16.0.3] --------------------------------------
[11:40:29 INF] [16.0.3] Telemetry Note:
[11:40:29 INF] [16.0.3] We use Application Insights to collect usage and error information in order to improve the quality of the tools.
[11:40:29 INF] [16.0.3] Currently we collect the following anonymous data:
[11:40:29 INF] [16.0.3] -Event data: application version, client city/country, hosting type, item count, error count, warning count, elapsed time.
[11:40:29 INF] [16.0.3] -Exceptions: application errors and warnings.
[11:40:29 INF] [16.0.3] -Dependencies: REST/ObjectModel calls to Azure DevOps to help us understand performance issues.
[11:40:29 INF] [16.0.3] This data is tied to a session ID that is generated on each run of the application and shown in the logs. This can help with debugging. If you want to disable telemetry you can run the tool with '--disableTelemetry' on the command prompt.
[11:40:29 INF] [16.0.3] Note: Exception data cannot be 100% guaranteed to not leak production data
[11:40:29 INF] [16.0.3] --------------------------------------
[11:40:29 INF] [16.0.3] Start Time: 09/25/2024 11:40:29
[11:40:29 INF] [16.0.3] Running with settings: {"SourceDomain": null, "SourceUserName": null, "SourcePassword": null, "TargetDomain": null, "TargetUserName": null, "TargetPassword": null, "ConfigFile": "configuration.json", "DisableTelemetry": false, "DebugTrace": false, "skipVersionCheck": false, "$type": "ExecuteMigrationCommandSettings"}
[11:40:29 INF] [16.0.3] OSVersion: Microsoft Windows NT 6.2.9200.0
[11:40:29 INF] [16.0.3] Version (Assembly): 16.0.3
[11:40:29 DBG] [16.0.3] DetectOnlineService::IsOnline
[11:40:29 WRN] [16.0.3] You are either not online or have chosen skipVersionCheck. We will not check for a newer version of the tools.
_
___ __ __ ___ ___ _ _ | | ___
/ _ \ \ / / / _ \ / | | | | | | | / _
| / > < | / | ( | || | | | | /
_| /_/_\ _| _| _,| __| _|

[11:40:29 DBG] [16.0.3] ===================================
[11:40:29 DBG] [16.0.3] Configuring 'MigrationTools:Processors:0:Enrichers'
[11:40:29 DBG] [16.0.3] ===================================
[11:40:29 INF] [16.0.3] Creating Migration Engine e24f4f8d-5601-4250-9141-3095f9999b17
[11:40:29 INF] [16.0.3] ProcessorContainer: Of 1 configured Processors only 1 are enabled
[11:40:29 INF] [16.0.3] ProcessorContainer: Adding Processor TfsWorkItemMigrationProcessor
[11:40:29 DBG] [16.0.3] Constructor found: IOptions1, TfsCommonTools, ProcessorEnricherContainer, IServiceProvider, ITelemetryLogger, ILogger1
[11:40:29 DBG] [16.0.3] Attempting to pass parameters: OptionsWrapper`1
[11:40:29 DBG] [16.0.3] ===================================
[11:40:29 DBG] [16.0.3] Configuring 'MigrationTools:CommonTools:FieldMappingTool:FieldMaps'
[11:40:29 DBG] [16.0.3] Configuring '0' as 'IFieldMapOptions' from 'MigrationTools:CommonTools:FieldMappingTool:FieldMaps'
[11:40:29 DBG] [16.0.3] Configuring '1' as 'IFieldMapOptions' from 'MigrationTools:CommonTools:FieldMappingTool:FieldMaps'
[11:40:29 DBG] [16.0.3] ===================================
[11:40:29 INF] [16.0.3] FieldMappingTool: Adding FieldMap FieldToFieldMap for SomeWorkItemType
[11:40:29 INF] [16.0.3] FieldMappingTool: Adding FieldMap FieldToFieldMap for SomeWorkItemType
[11:40:29 INF] [16.0.3] Logging has been configured and is set to: unknown.
[11:40:29 INF] [16.0.3] Max Logfile: Verbose.
[11:40:29 INF] [16.0.3] Max Console: Debug.
[11:40:30 INF] [16.0.3] Max Application Insights: Error.
[11:40:30 INF] [16.0.3] The Max log levels above show where to go look for extra info. e.g. Even if you set the log level to Verbose you will only see that info in the Log File, however everything up to Debug will be in the Console.
[11:40:30 INF] [16.0.3] Beginning run of 1 processors
[11:40:30 INF] [16.0.3] Processor: TfsWorkItemMigrationProcessor
[11:40:30 INF] [16.0.3] Migration Context Start: TfsWorkItemMigrationProcessor
[11:40:30 DBG] [16.0.3] WorkItemMigrationContext::InternalExecute
Error logged to Elmah.io!
!! Check for latest version - We fix issues constantly - If not, please create a discussion on https://github.com/nkdAgility/azure-devops-migration-tools/discussions so we can get this fixed !!
[11:40:31 FTL] [16.0.3] Validation of your configuration failed:
The configuration entry at 'MigrationTools:Endpoints:Target2' did not pass validation!
Please check the following failures:
-The AccessToken must not be null or empty when AuthenticationMode is set to 'AccessToken'.
[11:40:31 INF] [16.0.3] TfsWorkItemMigrationProcessor completed in 00:00:00
[11:40:31 ERR] [16.0.3] TfsWorkItemMigrationProcessor The Processor MigrationEngine entered the failed state...stopping run
[11:40:31 INF] [16.0.3] Command ExecuteMigrationCommand completed in 00:00:01.8590786

0 replies

Nikkath15 · 2024-09-25T18:54:36Z

Nikkath15
Sep 25, 2024
Author

configuration.txt

1 reply

MrHinsh Sep 25, 2024
Maintainer

This config does not match the log.

Log has "Target2", the config you posted has "Target"...

Nikkath15 · 2024-10-03T18:54:31Z

Nikkath15
Oct 3, 2024
Author

Hello Team,

Thank you for your assistance in resolving my previous issue. I successfully migrated all work items(799 items) from the source to the destination. However, I have encountered a scenario that requires clarification.

In the source, we have a work item type called "Opportunity," which does not exist in the target. I mapped it to the "User Story" work item type in the target. However, both the source and target already have a "User Story" work item type.

Only for the "User Story" work item type do we have a field called "Story Type" in both the source and target. To differentiate between the migrated "Opportunity" work items and the existing "User Story" work items, I would like to update the "Story Type" field in the target. This field has two values: "Story" and "Spike/Opportunity." For the migrated "Opportunity" work items, I want to set the "Story Type" to "Spike/Opportunity."

For the original "User Story" work items in both the source and target, the "Story Type" should remain as "Story."

In the source, we do not have a "Story Type" field for the "Opportunity" work item type, but we do have it in the target because its getting migrated as 'user story'. Additionally, for the existing "User Story" work items in the source, we need to map their "Story Type" field to the target.

I have attached the configuration file, but it is not functioning as expected. I set the default value to "Spike/Opportunity" for all opportunity migrated as user stories work item type, which resulted in all of them being updated to "Spike/Opportunity." If I do not specify a default value under the "Opportunity" block, all entries default to "Story."

I suspect there may be an issue with how I am referencing the field called System.WorkItemType for the "Opportunity" work item type.

In source story type is referred as xxxx.StoryType , in target its referred
configuration.txt
as Custom.StoryType

Could you please provide guidance on how to handle this mapping and updating process?

Thank you!

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

RefectedWorkItemId field value cannot be null #2391

{{title}}

{{editor}}'s edit

{{editor}}'s edit

Replies: 5 comments 1 reply

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

Select a reply

RefectedWorkItemId field value cannot be null #2391

Nikkath15 Sep 24, 2024

Replies: 5 comments · 1 reply

nkdagility-actions-bot[bot] bot Sep 24, 2024

MrHinsh Sep 24, 2024 Maintainer

Nikkath15 Sep 25, 2024 Author

Nikkath15 Sep 25, 2024 Author

MrHinsh Sep 25, 2024 Maintainer

Nikkath15 Oct 3, 2024 Author

Nikkath15
Sep 24, 2024

Replies: 5 comments 1 reply

nkdagility-actions-bot[bot]
bot Sep 24, 2024

MrHinsh
Sep 24, 2024
Maintainer

Nikkath15
Sep 25, 2024
Author

Nikkath15
Sep 25, 2024
Author

MrHinsh Sep 25, 2024
Maintainer

Nikkath15
Oct 3, 2024
Author