[#JRA-6800] CSV Importer should be able to import multiple values for a field

JIRA

CSV Importer should be able to import multiple values for a field

Created: 26/May/05 06:36 PM Updated: 26/May/08 06:19 AM

Component/s:

Import / Export

Affects Version/s:

None

Fix Version/s:

None

Time Tracking:

Not Specified

Issue Links:

Reference

This issue relates to:

JRA-5774 CSV Importer Improvements

Participants:	Anton Mazkovoi [Atlassian], Brian Nguyen, Carrie, mameha, Terry [Atlassian], Vlad B and Yuen-Chi Lian [Atlassian]
Since last comment:	49 weeks, 3 days ago
Support reference count:	3
Labels:

Description

« Hide

This is especially useful when importing components and versions. If you want to import the components "Component1, Component2" this will be parsed as 1 component instead of 2.

The current workaround for this is to create separate columns for each value and both map them to the same field.

All

Comments

Work Log

Change History

Sort Order:

Ascending order - Click to sort in descending order

[ Permlink | « Hide ]

Terry [Atlassian] - 17/Jul/06 01:20 AM

The workaround described here only works for component/version field. It does not work for multi-user picker field (custom field).

[ Permlink | « Hide ]

Yuen-Chi Lian [Atlassian] - 03/Oct/06 02:54 AM

The hack being applied at DefaultJiraDataImporter should look for values at a more abstract level, e.g. AbstractMultiSettableCFType, AbstractMultiCFType, etc.

–
Cheers,
Yuen-Chi Lian

"I do not seek. I find." - Pablo Picasso

[ Permlink | « Hide ]

Vlad B - 26/Oct/06 01:11 PM

Is this ever going to be fixed? It doesn't seem like it would take that long. Just curious for an update.

[ Permlink | « Hide ]

Carrie - 27/Jun/07 03:16 AM

Not able to handle custom fields with multiple values... This looks more like a bug to me

[ Permlink | « Hide ]

mameha - 30/Jul/07 01:55 AM

Looks like I have to update more than 1000 records by hand now thanks to this bug. Is it really so hard to fix?

[ Permlink | « Hide ]

Anton Mazkovoi [Atlassian] - 31/Jul/07 04:45 AM

Zac,

This is not very easy to fix, as custom fields are, well, custom. Solving the problem for a set of known custom fields is not as hard as fixing it completely, but that would leave holes for other custom fields. However, the main problem is looking at this issue in preference to many others and having the resources to address each one.

Cheers,
Anton

[ Permlink | « Hide ]

Carrie - 07/Aug/07 01:52 AM

Just some additional info. I was not able to import multiple values for "Components," but was able to import multiple values for custom field "Multi Select."

[ Permlink | « Hide ]

Anton Mazkovoi [Atlassian] - 08/Aug/07 02:14 AM

Carrie,

The best thing to do is to create support request in our support system:
http://support.atlassian.com

Our support guys should be able to help.

Cheers,
Anton