Getting error when wi-import if an Epic in JIRA linked by issue

[shankar5885]

Error: [E][16:10:59] '[Added] PROJ-4/-1->PROJ-8/-1 [System.LinkTypes.Hierarchy-Reverse]' - target work item for Jira 'PROJ-8' is not yet created in Azure DevOps/TFS. [W][16:10:59] ''PROJ-4', rev 0' - not all changes were saved.

link-map in config-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" } ]

Thank you.

AB#5954

[madkoo]

@shankar5885 Hi, try to add { "source": "Child", "target": "System.LinkTypes.Hierarchy-Forward" } to you're link mapping configuration

[shankar5885]

Hi @madkoo , Thank you for reply, Still i am getting same error

Please find updated link mapping config in my config-scrum.json "link-map": { "link": [

  { "source": "Child", 
    "target": "System.LinkTypes.Hierarchy-Forward" 
  },
  {
    "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"
  }
]

}

[RoyalWulf]

Hi, I am getting the same error. Has this been fixed? Cheers

[Alexander-Hjelm]

@RoyalWulf if this is indeed a bug, then no fix has been worked on yet to my knowledge.

I’m wondering if perhaps you have links to issues in other projects? Or otherwise links to issues that are outside of the migration svope? Could that be the problem?

[RoyalWulf]

@RoyalWulf if this is indeed a bug, then no fix has been worked on yet to my knowledge.

I’m wondering if perhaps you have links to issues in other projects? Or otherwise links to issues that are outside of the migration svope? Could that be the problem?

Hi, Thank you for your quick reply. The issue is in the same project and in scope of the migration. I am migrating the whole project.

I have lots of these errors with issues linked to Epics. It seems that issues created before the Epic is a problem

[Alexander-Hjelm]

Is it possible to do the migration in 2 steps? First the epics and then the issues? As a workaround got now

[RoyalWulf]

will try that

[Alexander-Hjelm]

Closed issue with the completion of #917. Please reopen this issue and @ me if the problem persists.

[jdshkolnik]

I just downloaded the latest release and am still hitting that same error.

[Alexander-Hjelm]

@jdshkolnik

Could you provide any additional information? Log files, configuration file and the relevant exported .json files would be helpful!