Component, Fix version migration with Solidify free version

[vani760]

Hi Team,

We are migrating issues from JIRA to ADO with solidify migrator tool(Free version),
most of the required fields we have migrated, but Fix version, component fields values not updated in ADO.
is there any limitation for free version of migrator tool? .
Attached Screen shots.. in Jira this fields i can see hyperlink or navigated fields

in ADO it is values , so its not mapping link values to normal values in ADO, is it possible in Free version of migrator or any limitation is there?

[Alexander-Hjelm]

Hello @vani760 !

The question is where you would like to migrate the fixesVersion field to?

Here is a simple field mapping which maps the field to a custom Single Line Text field in ADO:

{
    "source": "fixVersions",
    "source-type": "id",
    "target": "Custom.Fixversions"
},

[vani760]

Hi @Alexander-Hjelm ,
it worked for Fix versions, is it same for Component Also but need to select picklist(string)? can i use like below?

{
"source": "Components",
"source-type": "id",
"target": "Custom.Components"
},

[vani760]

For component also it worked, thank you so much for your support.

but is there any way to migrate linked issues

[Alexander-Hjelm]

Issue links should be preserved without changing the sample configs.

You can use the link-map section of the config to specify what types of links should be mapped. See the example configuration here: https://github.com/solidify/jira-azuredevops-migrator/blob/master/docs/config.md#example-configuration

It could be that you need to add the missing link types to your link map.

Here is a reference sheet over the default link types in Azure DevOps: https://github.com/solidify/jira-azuredevops-migrator/blob/master/docs/faq.md#4-i-need-to-obtain-a-field-reference-namelink-type-in-azure-devops

Read more about linked issues in single project vs multiple projects scenarios: https://github.com/solidify/jira-azuredevops-migrator/blob/master/docs/faq.md#5-guideline-for-migrating-multiple-projects

[vani760]

For (Blocks and relates ) to in Jira XML i can see like this, Could you please help with the me mapping

[Alexander-Hjelm]

I grabbed the following example from this issue: #1046

        {
          "source": "Relates",
          "target": "System.LinkTypes.Related"
        },
...
        {
          "source": "Blocks",
          "target": "System.LinkTypes.Dependency-Forward"
        }

[vani760]

Hi @Alexander-Hjelm
ok, i will try this and let you know.
Thank you

[vani760]

Hi @Alexander-Hjelm

i have added this but still this is not imported, only parent and child links coming thats it

Mapping:

ADO

[Alexander-Hjelm]

Looks right. There could be any number of things going on though.

Try running the Export again in force mode, for example, if you haven't already?

[vani760]

yea, i have tried but still not coming only parent, child relation coming .
linked issues not importing.

or is there any limitation? as we are using Free version on Migrator tool for Atlassian jira cloud to ADO

[Alexander-Hjelm]

Are the linked issues in the same project or in a different one?

[vani760]

its from same project

we are migrating from same project in Jira to ADO

[Alexander-Hjelm]

Ok! Then related issues should be migrated over.

I am not sure of the cause right away. Are you using the correct Jira Link Type? Have you defined custom jira link types that override the default ones?

[vani760]

Do i need to create custom column in ADO for linked Issues?

we have below linked issue types in Jira so how i need to create in ADO?
 
is blocked by
blocks
is cloned by
clones
is duplicated by
duplicates
is part of
is parent of
implements
relates to
is a test of
is tested by

in JIRA:

only parent and child links are coming..

[Alexander-Hjelm]

Do i need to create custom column in ADO for linked Issues?

No that should not be neccessary!