Custom Field in Jira not exporting the data correctly, fields missing in export about jira-azuredevops-migrator

[advitakhadke24]

To reproduce the issue,

1. Create a ticket in jira with following fields Client: Custom field Fix Version/s: System defined
   

2. Try exporting with above 2 fields populated

[Alexander-Hjelm]

See the FAQ for guidelines on how to map custom fields: https://github.com/solidify/jira-azuredevops-migrator/blob/master/docs/faq.md#3-how-to-map-custom-field

The Fixes Version field has the field ID "fixVersions" under the hood

[advitakhadke24]

Field Id "fixVersions" did work for me. Thankyou!

For the other custom field its a drop down field so I have I tried using Map Array for this i.e
{
"source": "customfield_10205",
"target": "Custom.ClientCode",
"mapper": "MapArray"
},

In the exported logs it says "the specific field contains unparsable type Null, using text"

Please find the attached log below

[Alexander-Hjelm]

The ClientCode field in your Jira view looks suspiciously like the tag field. Could it maybe do the trick to use the mapper "MapTags"?

The debug message means that the field does not have a value on the first revision. This could be expected or not, depending on when in the changlog you modified the ClientCode field.

[advitakhadke24]

Tried with the "MapTags" still no luck in getting this populated
{
"source": "customfield_10205",
"target": "Custom.ClientCode",
"mapper": "MapTags"
},

[advitakhadke24]

Along with the ClientCode field I am experiencing issues with 2 other custom fields i.e SN Case# and SN Incident# for these 2 fields the values are getting exported correctly from Jira as you can see in the attached json. But on importing it to ADO it gets populated with random value "98654321" and even though in the config file the field is defined once it gives error saying

" Update to work item 28623 had two or more updates for field with reference name 'Custom.ServiceNow_Incident'. A field cannot be updated more than once in the same update.
[E][10:35:14] Work Item 28623 failed to save."

Attachments:

Solidify.docx

[Alexander-Hjelm]

Try to specify the full FieldReferenceName for all of your fields in the config?

e.g. ServiceNow_Incident becomes Custom.ServiceNow_Incident

Also here I can see that you have many cases of using the Display name of the target fields (ADO) instead of the FieldReferenceName. This might affect your experience with the tool negatively, although I cannot say exactly what the consequences will be:

      {
        "source": "customfield_16300",
        "target": "Impact Score",
        "mapper": "MapInteger"
      },
      {
        "source": "customfield_16301",
        "target": "Effort Score",
        "mapper": "MapInteger"
      },
      {
        "source": "fixVersions",
        "target": "Fix Version",
        "mapper": "MapString"
      },
      {
        "source": "customfield_16302",
        "target": "Priority Rank",
        "mapper": "MapInteger"
      },
      {
        "source": "Developer",
        "target": "Dev Assignee",
        "mapper": "MapUser"
      },
      {
        "source": "Assignee",
        "target": "Dev Assignee",
        "mapper": "MapUser"
      },

You can find some troubleshooting steps related to migrating custom fields here: https://github.com/solidify/jira-azuredevops-migrator/blob/master/docs/faq.md#troubleshooting-my-custom-field-is-not-migrated-correctlynot-migrated-at-all

[advitakhadke24]

Thank you so much! I was able to get the ServiceNow_Incident fields populated. It was my mistake—I was looking at the wrong ADO process template. Our user story has this field defined with a different name compared to bugs. However, for the Client Code, I am still unable to figure out what’s going wrong. I would really appreciate it if you could help me with this.

I have tried specifying with the suggested Custom fields it's showing blank ' ' on exporting:
Attachments:

[advitakhadke24]

To add to the above

When there is multiple clients it understands that and mapps " ; " where as when there is single client it shows ' '

[Alexander-Hjelm]

@advitakhadke24 Have you tried to map both by "name" and "id"? As mentioned here: https://github.com/solidify/jira-azuredevops-migrator/blob/master/docs/faq.md#3-how-to-map-custom-field

[advitakhadke24]

@Alexander-Hjelm Yes the first highlighted in the screenshot is mapped with "name" and the other is with "Id"

[Alexander-Hjelm]

source-type cannot have the value "Client", it must either be "name" or "id".

[advitakhadke24]

Got it, I have tried with the source-type = Name since the values are like KI, AJ, AH

  {
    "source": "Client",
    "source-type": "Name",
    "target": "Custom.ClientCode"
  },
  
And just to be sure I have also tried with ID as well, still no luck!  
  
  {
    "source": "Client",
    "source-type": "id",
    "target": "Custom.ClientCode"
  },

[Alexander-Hjelm]

If using:

"source-type": "id",

Then the source should be the custom field key. Something like customfield_12345. You may need to use the REST API to retrieve this data.

[advitakhadke24]

Can you please explain on how to achieve this? If you have any document which I can follow to identity this?
Thanks!

[Alexander-Hjelm]

The only document we have with known solutions is here: https://github.com/solidify/jira-azuredevops-migrator/blob/master/docs/faq.md#3-how-to-map-custom-field

[advitakhadke24]

I did some research and it looks like there are 2 ways to find they custom field in ADO through ADO web portal or via API. I have already looked through web portal by going to Process -> work item type(User Story , Bugs)->Select the Custom Field
looks like custom field key in Jira is displayed as "Field reference name" in ADO

[Alexander-Hjelm]

Hum... What type is the field Custom.ClientCode in Azure DevOps? Is it a picklist? If so, maybe the value you are trying to import is not among the selectable values?

The value will effectively be a string containing the elements separated by commas.

[advitakhadke24]

Yes the "Custom.ClientCode" in Azure DevOps is a picklist and it is present in the picklist group.

Also, field has option to typein if not available in picklist

Another thing to note, there is another field which is also a picklist "labels" this works fine with the Maptags

[Alexander-Hjelm]

@advitakhadke24 For experimentation purposes, what you happen if you were to create a new Test field in your target Work Item Type process model and map the ClientCode field to that? Does the full value come over then? Or does it not change the value at all?

[advitakhadke24]

I tried adding a new test client code field - with a single line text field

Tried with Mapstring & tag
{
"source": "customfield_10205",
"target": "Custom.TestClientCode",
"mapper": "MapString"
},

 {
    "source": "customfield_10205",
    "target": "Custom.TestClientCode",
    "mapper": "MapTags"
  },

It just gives blank on exporting itself
[D][13:42:10] Mapped value ' ' to field 'Custom.TestClientCode'.

[Alexander-Hjelm]

Try MapArray?

https://github.com/solidify/jira-azuredevops-migrator/blob/master/docs/config.md#mappers

[advitakhadke24]

I have already tried that, if you see the comment here #1004 (comment)

I gave another shot this morning with test as well as the orignal Client field but still it's the same ' '

  {
    "source": "customfield_10205",
    "target": "Custom.TestClientCode",
    "mapper": "MapArray"
  },

[advitakhadke24]

@Alexander-Hjelm anything else I could try? We want this field migrated and thinking off getting Pro migrator tool...In case we do purchase ..will that be helpful to get this field populated?

[github-actions]

This issue is stale because it has been open for 25 days with no activity.

[github-actions]

This issue was closed because it has been inactive for 5 days since being marked as stale.