Defect #35131
Issue import - allow auto mapping for Unique ID and relation type fields
| Status: | Closed | Start date: | ||
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: |  Go MAEDA | % Done: | 0% | |
| Category: | Importers | |||
| Target version: | 4.2.1 | |||
| Resolution: | Fixed | Affected version: | 4.2.0 |
Description
Auto field mapping feature is absolutely awesome!
It works fine for all custom fields, but the mapping fails for 'Unique ID'. What can be wrong?
I would kindly appreciate any help!
ImportIssue_2.PNG - Field mapping works 2 (20.7 KB)
ImportIssue_3.PNG - Unique ID not mapped automaticaly (52.2 KB)
ImportIssue_1.PNG - Field mapping works 1 (41.6 KB)
0001-Allow-Unique-ID-and-relation-fields-to-be-auto-mappe.patch 
(3.28 KB)
Related issues
Associated revisions
Allow Unique ID and relation fields to be auto mapped (#35131).
Patch by Marius BALTEANU.
History
#1
Updated by Marius BALTEANU 2 months ago
- Status changed from New to Confirmed
- Assignee set to Marius BALTEANU
- Target version set to 4.2.1
Thanks Zoltán for reporting this issue, it seems that it was not implemented.
It will be fixed it in the upcoming 4.2.1.
#2
Updated by Marius BALTEANU 2 months ago
- Related to Feature #22913: Auto-select fields mapping in Importing added
#3
Updated by Marius BALTEANU about 1 month ago
- File 0001-Allow-Unique-ID-and-relation-fields-to-be-auto-mappe.patch added
- Subject changed from Issue import - field mapping -unique id auto-maping fails to Issue import - allow auto mapping for Unique ID and relation type fields
- Assignee deleted (
Marius BALTEANU)
Here is the patch to fix the auto mapping for Unique ID field and also for relation type fields.
#4
Updated by Go MAEDA about 1 month ago
- Status changed from Confirmed to Closed
- Assignee set to Go MAEDA
- Resolution set to Fixed
Committed the fix. Thank you.