Custom Field not getting mapped from Jira to ADO about jira-azuredevops-migrator

[Alexander-Hjelm]

The entry in your config looks weird: "source": "Component/s"

Confirm that this is the correct name of the field? You might need to do a Rest API query to find the correct key of the issue field.

[shweta22992]

Hi @Alexander-Hjelm I checked in the rest response and I could see different name like below -
"components": [
{
"self": "https://xxxxrest/api/2/component/xxx",
"id": "16163",
"name": "comp"
}
]
but after changing the name in config still it didnt get map
{
"source": "components",
"target": "tF Components",
"mapper": "MapArray",
"for":"Epic,Feature,Task,User Story,Bug"
}
Is there something I am missing here

[Alexander-Hjelm]

Are you sure that the reference name of the field in ADO is actually "tF Components"? This looks strange. Are you maybe using the field name instead? Usually spaces are not allowed in the reference name.

[shweta22992]

Thanks @Alexander-Hjelm it is working now. Worked with the field name also had previously made a wrong file update thats why couldnt see the update. Its now mapping fine.
Just one more doubt in this, I want to map 2 different JIRA fields into a single ADO field is there a way to do that

[Alexander-Hjelm]

Field consolidation is a PRO feature only. You can read more about the PRO version, which is currently in an early adopter evaluation phase, here: https://github.com/solidify/jira-azuredevops-migrator#jira-azure-devops-migrator-pro

You can also use the contact information there to inquire about purchasing the PRO version :)

[shweta22992]

Got it, thanks.