Comments (14)
That sounds about right!
from jira-azuredevops-migrator.
In theory, the import should not be affected if you do one batch after the other and follow the guidelines here: https://github.com/solidify/jira-azuredevops-migrator/blob/master/docs/faq.md#scenario-2-multiple-projects
The links would be skipped on the first pass, but set up properly on the second pass, once both the source and target work items are present in the target project.
from jira-azuredevops-migrator.
So just to verify i understand the process, the recommendation will be:
Export:
- Set "download-options": 0
- Force = true
- Export each config into a separate workspaces in parallel
Import:
- Import one workspace at a time
- DON'T use force
- After every import completes, copy the itemsJournal.txt from one workspace to the next, this will ensure mappings of the items and will continuously get updated on every import.
Did i get it right? Anything missed?
from jira-azuredevops-migrator.
Hey,
Following the process above,
Do you possibly have an idea why i'm getting these errors in the import?
[I][15:09:11] Processing 5614/147165 - wi '1853211', jira 'TST-10220, rev 5'
[E][15:09:11] Input string was not in a correct format.
[W][15:09:11] ''*****-13729', rev 9' - not all changes were saved.
The only thing that this revision contains is a relation addition to an item that has already been imported and exists in the Azure DevOps.
{
"Author": "",
"Time": "",
"Index": 9,
"Fields": [],
"Links": [
{
"Change": 0,
"TargetOriginId": "****-4508",
"TargetWiId": 0,
"WiType": "System.LinkTypes.Hierarchy-Reverse"
}
],
"Attachments": [],
"DevelopmentLink": null,
"AttachmentReferences": false
},
This causes many links to get skipped and then end result is that the items don't have the relations.
from jira-azuredevops-migrator.
Looks like maybe the itemsJournal file was corrupted? Check it and verify that there are no empty lines and that there are no other weird things going on.
from jira-azuredevops-migrator.
I see this warning in the import log:
[W][20:54:23] Detected unicode characters, removed.
[W][20:54:23] Detected unicode characters, removed.
[W][20:54:27] Detected unicode characters, removed.
Could be related?
Though i don't see any corruption in the itemsjournal .
In addition, i checked if the item that it's trying to add in that revision appears inside the itemsjournal and it's indeed there.
from jira-azuredevops-migrator.
Should be fine. The unicode character warning comes from this PR: #706, which solved another error related to characters that could not be properly parsed.
from jira-azuredevops-migrator.
So any thoughts why this is happening?
What could be the issue leading to this error?
We see that most links are migrated properly, but we see many errors like described above which are failing to link.
Worth mentioning the itemsjournal is over 100K lines during the process run.
from jira-azuredevops-migrator.
Not sure straight away. Here is the line which is logging the above error:
Logger.Log(LogLevel.Info, $"Processing {importedItems + 1}/{revisionCount} - wi '{(wi.Id > 0 ? wi.Id.ToString() : "Initial revision")}', jira '{executionItem.OriginId}, rev {executionItem.Revision.Index}'.");
I am not sure, but it seems like the expression (wi.Id > 0 ? wi.Id.ToString() : "Initial revision")
results in an empty string? Any idea why that could be?
from jira-azuredevops-migrator.
I'm sorry, the ID was mistakenly deleted.
It does exist, like here:
Processing 5614/147165 - wi '1853211', jira 'TST-10220, rev 5'
I think it's failing here:
Which means for some reason the incomplete = true
Which is probably happening here:
Probably failure is here:
https://github.com/solidify/jira-azuredevops-migrator/blob/304e6e2f5692e6211ab6b40e154f0702fdc670c3/src/WorkItemMigrator/WorkItemImport/Agent.cs#L651C55-L651C68
Which is related to the itemsjournal.txt :(
from jira-azuredevops-migrator.
Seems like it's failing here:
int sourceWiId = _context.Journal.GetMigratedId(link.SourceOriginId);
Cause if it was failing here:
int targetWiId = _context.Journal.GetMigratedId(link.TargetOriginId);
It would have gotten into :
if (link.TargetWiId == -1)
{
var errorLevel = Settings.IgnoreFailedLinks ? LogLevel.Warning : LogLevel.Error;
Logger.Log(errorLevel, $"'{link}' - target work item for Jira '{link.TargetOriginId}'" +
$" is not yet created in Azure DevOps/TFS. You can safely ignore this warning if" +
$" this work item is scheduled for import later in your migration.");
success = false;
continue;
}
from jira-azuredevops-migrator.
Ok! I see now that the Author and Datetime stamp of the issue has not been set, which indicates an internal failure in the Exporter. Did the JiraExport result in any obvious errors? Check the log maybe.
from jira-azuredevops-migrator.
They have also been set, but removed so no internal data is published.
Sorry for misleading.
from jira-azuredevops-migrator.
Hi @Alexander-Hjelm ,
Updating we have managed to solve the issue by one small change.
In the export section, instead of setting "download-options": 0, we have set it to 7.
Then, copied itemsjournal and Imported without force.
This way it ensures that the migration passes including all its relations.
Thank you so much for your assistance!
from jira-azuredevops-migrator.
Related Issues (20)
- Import all the fields of Test case instead of few fields. HOT 1
- Is there a version of application which is supporting Jira with extension structure HOT 15
- Development / Releases are supported? HOT 6
- show round time in effort field HOT 12
- Jira Users are not getting migrated HOT 1
- Description Field Blank in ADO User Story HOT 3
- Flat Migration HOT 3
- Add support for development links to non-migrated GitHub repositories
- Support for Continuing an Import at a Specific Revision HOT 4
- how can I use the tool if I have issue types Test and Test Plan and I don't have Task or sub task or any issue types else on jira ? HOT 3
- Linked issue is lost during the import/export process HOT 1
- Workitem Linking not working as expected HOT 3
- Sprint information is not exporting HOT 10
- Attachments are not exporting HOT 15
- Wrong Sprint Information Exporting HOT 7
- Cross-project Parent links not established when migrating with download option 0 HOT 6
- MapArray errors to map null/None value HOT 3
- jira export is failing HOT 2
- Jira export - Unexpected migration error. [System.InvalidCastException] HOT 1
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 jira-azuredevops-migrator.