Bulk upload epics, features, stories

[Michael Warhola]

Looking for a CSV template to bulk import epics, features, and stories into JIRA project. On latest data server version

Hierarchy we use is Epic -> Feature -> Story

Need the file so that Features will map to Epics and Stories will map to Features
Also need template to map Features to EPICs that have already been entered into JIRA.

Have a field called EPIC Link that the feature will map to and a field called Linked Issue that will be marked as child of Feature

Fields to import include summary, description but want a template that includes all available fields should we use more in the future

[Anne Saunders]

I've built my spreadsheet over a long period of time, and refined it to the point that we consider it a confidential internal tool, but I think I can help.

A good place to start is by exporting your issues from Jira as a spreadsheet, so you can see the fields you need laid out for you. Then you can make a copy of the export as a template for imports and add new issues with the relationships you want them to have.

Here are the columns in my spreadsheet, in order: 

• "Issue id"
  • The number part of the issue key; you'll specify the project during import)
• "Issue Type"
• Summary
• Description
• Label1
• Label2
• Priority
• "Due Date"
  • Needs to be in a SimpleDateFormat
• Assignee
  • the User's Atlassian alphanumeric ID, which you can find by searching for them as an assignee or reporter in the Filters > Advanced issue search activity
• Status
  
  • Select from your workflow (or omit)
• "Epic Link"
  • The Epic's issue key, used to connect a Feature to an Epic
• "Parent ID"
  • The Feature's issue key, used to connect a Story to a Feature
• "Original Estimate"
  • in seconds

[Barford, Zak]

Hi Anne, 

Are you able to import stories that link to features that link to epics within one CSV?

How do you let Jira know to link to a feature that has only just been created?

Kind regards

Zak

[Anne Saunders]

The Parent Column takes care of that. In the past, I've also used columns for related issues where you have an inward or outward link, type of link (blocks/blocked by, creates/created by, relates to, etc.).

The import process creates all of the issues in the CSV, then performs the links, so as long as the issue exists in the project or gets created in the import, it can be referenced as a link. (Whether Parent or related issue)