nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

JIRA Import issue - Importing from CSV creates new custom fields

unknown

Hello,

we have a problem when trying to import issues into JIRA from a CSV file.

In the CSV file we have the values which should be set in the Custom Fields in JIRA.

These custom fields are mostly type Select List so we tried to use the mapping (map the value from CSV to the value in Select list) but it didn't work - the existing values were not displayed.

When we continued with the import JIRA actualy created new global custom fields with the same name as the already existing custom fields which is very bad.

We had to delete all the imported issues (more than 250) and delete all the new custom fields manually to restore JIRA to where it was before the import.

Our JIRA version is 4.4.4., Importers plugin 3.5.3

Accepted answers

Pawel Niewiadomski

Hi,

I agree there should be a select box to select values from an existing custom field but there's none. We haven't implemented it yet. I raised https://studio.atlassian.com/browse/JIM-731 for that, anyone interested please vote.

I guess new custom field is created because the one in JIRA has a limited context - like it's defined only for some projects or issue types. Am I guessing correctly?

JIM 3.x allows you to import only to global custom fields, it may show the custom field on the list, but later it will create a new one if it can't find a global custom field. I think there's a message in the log about that.

Cheers,

Pawel

All comments

Ramiro P

Hi, if I remember well in one step you choose what Custom Field will be mapped with what column of the CSV File. And then in order to select the values, you have to write in those text box you marked the value of the Select Custom Field. I'm not sure, but I think the values have to be already created in the custom field before doing the import.

Pawel Niewiadomski

Hi,

I guess new custom field is created because the one in JIRA has a limited context - like it's defined only for some projects or issue types. Am I guessing correctly?

Cheers,

Pawel

unknown

Hi Ramiro,

yes we have the values already created in the existing custom fields but the import just creates whole new custom fields instead of using the already existing fields with values.

unknown

Hi Pawel,

thank you for your reply.

Our custom fields are also limited for a specific issue type on one project so that could be the reason why the import did not work.

Atleast now we know the error is not on our side, but still we need to find another way to import the data. I was thinking about an using SQL query to the DB instead.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

csv

custom-field

jira

import

field