question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

"WorkItemTypeDefinition" do not working

See original GitHub issue

Hi.

In configuration I set “WorkItemTypeDefinition”: { “Bug”: “Bug”, “Code Review Request”: “Code Review Request”, “Code Review Response”: “Code Review Response”, “Epic”: “Epic”, “Feature”: “Feature”, “Feedback Request”: “Feedback Request”, “Feedback Response”: “Feedback Response”, “Shared Parameter”: “Shared Parameter”, “Shared Steps”: “Shared Steps”, “Task”: “Task”, “Test Case”: “Test Case”, “Test Plan”: “Test Plan”, “Test Suite”: “Test Suite”, “User Story”: “Product Backlog Item”, “Issue”: “Impediment” },

But when I start migration, I get an exception

[ User Story][Complete:1/4][sid:2 |Rev:3 ][tid:null | …FAILED to Save [ User Story][Complete:1/4][sid:2 |Rev:3 ][tid:null | System.Exception: WARNING: Unable to find ‘User Story’ in the target project. Most likley this is due to a typo in the .json configuration under WorkItemTypeDefinition! at VstsSyncMigrator.Engine.WorkItemMigrationContext.CreateWorkItem_Shell(Project destProject, WorkItem currentRevisionWorkItem, String destType) in D:\a\1\s\src\VstsSyncMigrator.Core\Execution\MigrationContex\WorkItemMigrationContext.cs :line 477 at VstsSyncMigrator.Engine.WorkItemMigrationContext.ReplayRevisions(List`1 revisionsToMigrate, WorkItem sourceWorkItem, WorkItem targetWorkItem, Project destProject, WorkItemStoreContext sourceStore, Int32 current, WorkItemStoreContext targetStore) in D:\a\1\s\src\VstsSyncMigrator.Core\Execution\MigrationContext\WorkItemMigrationContext.cs:line 335 [ User Story][Complete:1/4][sid:2 |Rev:3 ][tid:null | System.NullReferenceException: Object reference no t set to an instance of an object. at VstsSyncMigrator.Engine.WorkItemMigrationContext.ProcessWorkItem(WorkItemStoreContext sourceStore, WorkItemStoreContext targetStore, Project destProject, WorkItem sourceWorkItem, Int32 retryLimit, Int32 retrys) in D:\a\1\s\src\VstsSyncMigrator.Core\Execution\MigrationContext\WorkItemMigrationContext.cs:line 195 migration.exe Warning: 0 : [EXCEPTION] System.NullReferenceException: Object reference not set to an instance of an object. at VstsSyncMigrator.Engine.WorkItemMigrationContext.ProcessWorkItem(WorkItemStoreContext sourceStore, WorkItemStoreContext targetStore, Project destProject, WorkItem sourceWorkItem, Int32 retryLimit, Int32 retrys) in D:\a\1\s\src\VstsSyncMigrator.Core\Execution\MigrationContext\WorkItemMigrationContext.cs:line 238 at VstsSyncMigrator.Engine.WorkItemMigrationContext.InternalExecute() in D:\a\1\s\src\VstsSyncMigrator.Core\Execution\MigrationContext\WorkItemMigrationContext.cs:line 124 at VstsSyncMigrator.Engine.MigrationContextBase.Execute() in D:\a\1\s\src\VstsSyncMigrator.Core\Execution\MigrationCo ntext\MigrationContextBase.cs:line 35 MigrationEngine: The Processor WorkItemMigration entered the failed state…stopping run

I have User Story WI in the source project and Product Backlog Item WI in the target project. Am I doing something wrong?

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Reactions:1
  • Comments:5

github_iconTop GitHub Comments

1reaction
CyberSaphirecommented, Mar 25, 2020

I encountered same issue, and tried older version v8.8.0 and it worked.

0reactions
github-actions[bot]commented, May 29, 2020

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 10 days

Read more comments on GitHub >

github_iconTop Results From Across the Web

Unable to import work item type definition
In an attempt to keep this simple I am simply exporting the product backlog item WIT and then immediately re-importing it to ensure...
Read more >
Add or modify a work item type - Azure DevOps Server
You can modify an existing work item type or add a custom work item type based on your team's tracking requirements or workflow...
Read more >
Empty Work Items · Issue #695 · nkdAgility/azure-devops- ...
While running the project getting the error for empty work items n Path) | Digital ... in the work item type definition file...
Read more >
Add and manage work item types - Azure DevOps
In this article ... You can add custom work item types (WITs) or modify existing WITs to add fields, remove or hide fields,...
Read more >
TF26027: A field definition Microsoft.Custom. ...
Hi Team, We are facing strange issue in our TFS aggregation . We had custom field Microsoft.Custom.Definition and we had defined rules for...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found