How do you import release versions via csv?

[Steve McKenzie]

When I imported my issues into my project via csv, I used the column FixVersion to specify my version.  This creates a version in the project, however, the status, start date and the released date don't get populated.  I don't see a jira field to map to these fields.  Is there a way to import versions with the attributes of status, start and release dates either within an issue import or by a release import?  I have only been able to get my versions created by mapping the FixVersion field.

[Dave Theodore [Coyote Creek Consulting] · Accepted solution]

You'll need to first create the versions and set them up the way you want.  When you import the data, choose to map the values in the CSV to the versions that you created in Jira. It's tedious, but it should do what you want. 

[liushyan]

Hi Dave, I have the same issue when I use CSV importing method to import all issues into a project on a Jira Cloud site. All the 'released' status of versions are shown as 'unreleased', the start date and release date is missing, and the Description field is populated with the version numbers rather than the original descriptions. 

Could you explain in more details of the solution you suggested? Thank you!

[Debra Jones]

I'm looking for this option too?

Would like to be able to 'import' our planned Releases with

• Version name
• Release Date
• Description

[Marquita Pruitt - External]

Seems to me that the accepted answer is not valid.  Original poster is trying to use the issue import function to create the versions - not create them and then edit them individually.  I would like to know how to create a new version with dates and description upon importing as well.

[Ansar Thennaden]

exactly, im waiting for the answer

[Tim Walker]

+1 we could sure use it! Thank you! 

[Carol Lage]

@Marquita Pruitt - External , @Ansar Thennaden and @Tim Walker, I posted below how I did a workaround to resolve that.
Let me know if you have any questions.

[Carol Lage]

Hi @Debra Jones,
I tried to create the Fix-version/Release using the import CSV, but it's only possible to add an existing value of the Fix-version to the card, as was commented.
So, my workaround was to create an automated rule to create all the Fix-version releases first, using a REST API, and then use the CSV import to add the dates to the issues.

Global automation manually triggered for all projects:

a) Create the web request with the URL of your Release page (find it in your Project>Releases on the left navbar). I changed the project's name to the smart value {{project}} to use this as a Global rule in multiple projects.





b) Add the component "Create version" with the information of each Fix version. In my case, we use the field Version Name with the date, but you can write what you want and use the Description field as you mentioned.


c) As was set to Manually trigger, you have to go to the board of every project that you want to create the Fix-version, click on one issue card and click in Automation>"Your rule's name" in the lightning icon.

*This rule will not delete or overwrite other Fix-versions that you could already have on your Release page. It will just add new ones.

You can check these posts for more details:
Bulk releasing of fix version 
Automation-for-Jira-Send-web-request-using-Jira-REST-API 

Adding the dates to the issues
After creating the Fix-versions, you can import the CSV file to fill the issues with the corresponding date you want. You must be Jira admin to do that.
Check these posts for that:
Import-data-from-a-csv-file 
CSV-Import 

Hope that help! :D
Let me know if you have any questions.

[Debra Jones]

Does anyone have an answer to this?

[Carol Lage]

Hi @Debra Jones,
I reply as an answer so you can vote if it works :)