Comments (17)
It was sillier than that, I was going from Scrum to Agile and my query contained User Story instead of Product Backlog Item and I was not linking Impediment to Issue.
from azure-devops-migration-tools.
Let take one as an example for debug:
LinkMigrationContext: Migrating Links for wiSourceL=5177
LinkMigrationContext: Cannot find twiTargetL matching wiSourceL=5177 probably due to missing ReflectedWorkItemID
Can you open up your target location in a browser and create a query that looks for 5177 in the ReflectedWorkItemId field?
What it looks like is that the field "ReflectedWorkItemId" does not exist in the target location, and thus there is no way for the tool to find the migrated work items.
from azure-devops-migration-tools.
Just attempted and it does not exist on the target or source.
from azure-devops-migration-tools.
You need to add that field to the target before you do a migration. This field will be populated with the ID from the old system and will be used by the other migrators to map your links and attachments from your source to the target.
Effectively what you migrate the links it will take the original source ID and look it up in the ReflectedWorkItemId of the new target location. If it finds a match for both ends of your link then it will add them.
Without the ReflectedWorkItemId field containing the source work item ID there is no way to migrate links or attachments.
from azure-devops-migration-tools.
understood and I have attached a screenshot of the field on the target. All of my work items have the ReflectedWorkItemId field.
from azure-devops-migration-tools.
Sorry, I thought that:
Just attempted and it does not exist on the target or source.
Can you then search for 5177 in that field? if it returns then we have a bug... somewhere...
from azure-devops-migration-tools.
Like so?
This query has been run with zero results on both the target and source.
from azure-devops-migration-tools.
ok, so that work item has not been migrated to the target.
If you look it up on the Source what is the work item type?
from azure-devops-migration-tools.
It is a User Story.
from azure-devops-migration-tools.
We're any of your User Stores migrated? There is no left hand side for WorkItemTypeDefinition that is User Story.
from azure-devops-migration-tools.
So I did a bit more digging and came to the conclusion that the reason those item ID's were not migrating is due to the fact that they have previously been migrated from TFS to VSTS which is somehow making them unable to be migrated again. anything created new in VSTS with attached links and files migrates fine minus the area path being removed.
from azure-devops-migration-tools.
@jaw2ay make sure to set the reflectedworkitemid field back to “” if some items were already migrated and you want to migrate again. Use a query + bulk editing
from azure-devops-migration-tools.
@MrHinsh If a Work Item is linked to another parent Work Item that is not in the scope of the query, it seems that I am losing that child Work Item in the migration. Is it safe to assume that this is correct? I am running a query on TFS that states I have 55k Work Items yet when I migrate I am left with around 16k Above epic is a custom work Item named Release that most work items are associated with in a Parent child way. I have not created a Release Work Item template on VSTS and I can only assume that this is my problem. Can you confirm this for me?
from azure-devops-migration-tools.
No this is not the case.
The WorkItemMigration does not look at links or attachments. Simply at what is in scope based on the query specified in QueryBit.
It should say, "xxx work items found" just after it starts the migration.
from azure-devops-migration-tools.
Can you share your QueryBit?
from azure-devops-migration-tools.
Sure it is just based on your sample that omits closed work items.
Sent the whole processor just to make sure I am doing this right.
{
"ObjectType": "VstsSyncMigrator.Engine.Configuration.Processing.WorkItemRevisionReplayMigrationConfig",
"Enabled": true,
"PrefixProjectToNodes": true,
"UpdateSoureReflectedId": false,
"QueryBit": "AND [Microsoft.VSTS.Common.ClosedDate] = '' AND [ReflectedWorkItemId] = '' AND [System.WorkItemType] IN ('Shared Steps', 'Shared Parameter', 'Requirement', 'Task', 'User Story', 'Bug', 'Feature', 'Test Suite', 'Test Plan', 'Test Case')"
},
from azure-devops-migration-tools.
You should remove Test Plan and Test Suite as there is no value in migrating them. New ones will be created by the Test Migrator.
Since you are omitting closed work items I would guess that's where the bulk of the missing items are...
from azure-devops-migration-tools.
Related Issues (20)
- Expecting comparison operator. The error is caused by «EQUALS».
- Expecting expression. The error is caused by «(».
- TF51012: The UNDER operator can only be used with classification fields. The error is caused by «[System.WorkItemType]».
- TF51005: la query fa riferimento a un campo inesistente. Errore causato da «[nkdScrum.ReflectedWorkItemId]».
- Identificatore vuoto non consentito. Errore causato da «[]».
- Il valore non può essere null. Nome parametro: str
- Rebuild Launcher with Specter Command and Seralog!
- Rename WorkItemUpdate to Bulk Edit
- FilterWorkItemsThatAlreadyExistInTarget is not filtering the workitems which is already migrated in the target HOT 1
- FixAreaPathAndIterationPathForTargetQuery Not Populating
- [Bug]: WorkItemMigration Fails with IOException HOT 1
- [Bug]: Related Link could not be read HOT 1
- [Bug]: TF26198: Unable to GetWorkItem with id[4601] During Azure DevOps Migration - Need Assistance to Skip Error and Continue Migration HOT 1
- An existing connection was forcibly closed by the remote host
- System.NullReferenceException: Object reference not set to an instance of an object HOT 3
- [Bug]: Issue with Migrating Test Plans and Test Suites: Work Item Not Ready to Save
- Sequence contains more than one element
- [Bug]: test HOT 2
- [Bug]: Error in TestPlansAndSuitesMigrationContext - TF237124: Work Item is not ready to save HOT 2
- [Bug]: Error: TF237124: Work Item is not ready to save during Test Plans, Test Suites, and Test Cases Migration using nkdAgility Azure DevOps Migration Tools HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from azure-devops-migration-tools.