Multiple custom field configurations not being mapping issue from JIRA to ADO

[Geethika-Krishnan]

Describe the problem

I am encountering an issue while using the tool for migrating items from JIRA to Azure DevOps (ADO). The problem arises when attempting to migrate items that have a custom field called "Severity," which uses a picklist for configuration. The custom field has different configurations over time, which seems to be causing the field to not be mapped and show a warning message instead.

Warning Message : [W][10:17:34] Missing mapping value '2 – High severity' for field 'customfield_10600' for item type 'Bug'. [W][10:17:35] Missing mapping value '3 – Medium severity' for field 'customfield_10600' for item type 'Bug'.

To Reproduce Steps to reproduce the behavior:

• Identify JIRA items that use the "Severity" custom field. • The older bug configuration have a set of picklist values. • Newer configurations were added with new picklist values. • Attempt to migrate these items to ADO using the migration tool.

Tool version v3.0.328

Attachments

• config.json RTE_POC.json

• jira-export-log.txt jira-export-log-240729-092846.txt

• wi-import-log.txt wi-import-log-240729-105834.txt

Screenshots

Configurations in JIRA

[Alexander-Hjelm]

I can confirm that legacy field values such as statuses, picklist values, user selectors, etc, will still be selected on the Jira Issues even if those values are removed in the process configuration and no longer selectable. You must map those values yourself in the field-map, either as existing values in the ADO picklist or by creating new values in the ADO picklist and assigning those.

In your case, the values which you must map are indicated by the warning messages:

[W][10:17:34] Missing mapping value '2 – High severity' for field 'customfield_10600' for item type 'Bug'.
[W][10:17:35] Missing mapping value '3 – Medium severity' for field 'customfield_10600' for item type 'Bug'.

You must resolve all such warnings by mapping the field values before the tool can migrate all of your data reliably.

[github-actions[bot]]

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

[github-actions[bot]]

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