Create a dummy project that uses the field.
Create CSV with two columns - summary and field value (you can use the same value for each line!)
Import the CSV into the empty project - it will create one issue per line, and, if you configure it correctly for import, create a new option for each one in your new field.
Delete the project, it won't affect your field
Thank you for your answer but I wanted some clarification.
First I will create a new project and add a new drop down custom field called (XYZ).
Next, I will create a csv file and have summary and XYZ columns
Test 1 X
Test 2 Y
Test 3 Z
This will create 3 new issues.
I will then assign this drop down to a the other project and delete the new dummy project?
Is this correct?
Thanks, I am attempting to import a test file, but a field is not available on the list in the mapping step. I noticed the fields not available are indicated as "...created by JIM during import process" on the "issues->Custom fields" page. Any tips? Actually I think just got it. The field needs to be global to all projects.
If you spend enough time as a Jira admin - whether you are managing a single, mid-sized instance, a large enterprise one or juggling multiple instances at once - you will eventually find yourself in ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot