Issue when exporting work items about jira-azuredevops-migrator

[MOlausson]

Thanks for reporting @hasithamgh. Can you share a little more context regarding your structure. Which issue types are you using? Which process? Do you use parent epics at all? And if possible share your migration config file.

[hasithamgh]

Thanks @MOlausson for looking in to this. I'm totally new to JIRA but I need to do a work item migration from JIRA to AzureDevOps. I'm currently using a test jira instance where it contains few users stories, tasks and bugs. I used the default config file given with the tool and just renamed the project names. I can grant you permission to the JIRA instance if you could provide your email address.`

{ "source-project": "SampleProject", "target-project": "JiraMigration", "query": "project = SampleProject ORDER BY Rank ASC", "workspace": "C:\\Temp\\JiraExport\\", "epic-link-field": "customfield_10008", "sprint-field": "customfield_10007", "batch-size": 20, "log-level": "Debug", "attachment-folder": "Attachments", "user-mapping-file": "users.txt", "base-area-path": "Migrated", "base-iteration-path": "Migrated", "ignore-failed-links": true, "process-template": "Scrum", "link-map": { "link": [ { "source": "Epic", "target": "System.LinkTypes.Hierarchy-Reverse" }, { "source": "Parent", "target": "System.LinkTypes.Hierarchy-Reverse" }, { "source": "Relates", "target": "System.LinkTypes.Related" }, { "source": "Duplicate", "target": "System.LinkTypes.Duplicate-Forward" } ] }, "type-map": { "type": [ { "source": "Feature", "target": "Feature" }, { "source": "Epic", "target": "Epic" }, { "source": "Story", "target": "Product Backlog Item" }, { "source": "Bug", "target": "Bug" }, { "source": "Task", "target": "Product Backlog Item" }, { "source": "Sub-task", "target": "Task" } ] }, "field-map": { "field": [ { "source": "summary", "target": "System.Title", "mapper": "MapTitle" }, { "source": "assignee", "target": "System.AssignedTo", "mapper": "MapUser" }, { "source": "description", "target": "System.Description" }, { "source": "priority", "target": "Microsoft.VSTS.Common.Priority", "mapping": { "values": [ { "source": "Blocker", "target": "1" }, { "source": "Critical", "target": "1" }, { "source": "Highest", "target": "1" }, { "source": "Major", "target": "2" }, { "source": "High", "target": "2" }, { "source": "Medium", "target": "3" }, { "source": "Low", "target": "3" }, { "source": "Lowest", "target": "4" }, { "source": "Minor", "target": "4" }, { "source": "Trivial", "target": "4" } ] } }, { "source": "customfield_10007", "target": "System.IterationPath", "mapper": "MapSprint" }, { "source": "labels", "target": "System.Tags", "mapper": "MapTags" }, { "source": "comment", "target": "System.History" }, { "source": "status", "target": "System.State", "for": "Task", "mapping": { "values": [ { "source": "To Do", "target": "To Do" }, { "source": "Done", "target": "Done" }, { "source": "In Progress", "target": "In Progress" } ] } }, { "source": "status", "target": "System.State", "for": "Bug,Product Backlog Item", "mapping": { "values": [ { "source": "To Do", "target": "New" }, { "source": "Done", "target": "Done" }, { "source": "In Progress", "target": "Committed" } ] } }, { "source": "status", "target": "System.State", "for": "Epic,Feature", "mapping": { "values": [ { "source": "To Do", "target": "New" }, { "source": "Done", "target": "Done" }, { "source": "In Progress", "target": "In Progress" } ] } }, { "source": "customfield_10004", "target": "Microsoft.VSTS.Scheduling.Effort", "for": "Epic,Feature,Product Backlog Item,Bug", "type": "double" }, { "source": "remainingEstimate", "target": "Microsoft.VSTS.Scheduling.RemainingWork", "for": "Bug,Task", "type": "double" }, { "source": "description", "target": "Microsoft.VSTS.TCM.ReproSteps", "for": "Bug" } ] } }

above is the config file used.

the project type I used in JIRA is 'software' with Scrum template.

thanks,
Hasitha

[srijampani]

@MOlausson , i am also running into the same issue, In our JIRA project we have Epics, Stories, bugs, tasks, sub tasks. EPIC's have tasks present under them, but not all tasks have Epics tied to them. Can you give any pointers on how to resolve this.

[MOlausson]

Fixed in v2.2.21.