Closed AnthonyRobinson closed 11 months ago
If you just need to map the value of the email address, I would try omitting the source-type
and mapper
in order to map the raw value. Perhaps try that?
Nope. Removing source-type and/or mapper has no effect. I am having no problems mapping simple "key":"value" Jira custom fields. I'm just having issues with more complex, nested custom fields.
I see that you would need a mapper that accesses the emailAddress
property of the customfield_10012
field then? Could that be correct?
Writing your own mappers is relatively straight forward. Until then we should think of finding a general solution to this problem in the form of a mapper where you can specify the name of the property that you want to access. I will create a feature request for this so that we can track it.
Writing your own mapper is relatively straightforward, if you wish to have a crack at it yourself! Simply add a new case to the switch at https://github.com/solidify/jira-azuredevops-migrator/blob/master/src/WorkItemMigrator/JiraExport/JiraMapper.cs#L87C27-L87C27, and write your own logic
This issue is stale because it has been open for 25 days with no activity.
This issue was closed because it has been inactive for 5 days since being marked as stale.
I need to map Jira custom fields with sub-email addresses into ADO WIs email fields. I have read the FAQ, but can't seem to generalize it to my problem.
I'm using v3.0.139
In Jira, my custom field looks like this:
And my target ADO WI field needs to look like this:
My (non-working) mapping in config.json looks like this:
I've tried quoting and un-quoting Custom.DBA.uniqueName in the config file, but no change.