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; } } }

How to import a template file in CSV format into Jira with epic, main tasks and substasks?

Dominika Włodarczyk

Hello, I have a file with a ticket template in CSV format that I would like to upload to Jira.

Can you advise me on how to upload and map field values? Should I have separate files for each column (epic, main tasks, and subtasks)?

Is it correct that e.g. an epic has to be mapped as Summary?

Accepted answers

Antuan Sammak

Hi @Dominika Włodarczyk

Welcome to the Atlassian Community!

when you are saying that you have a file with a ticket template, can you please explain a bit further what do you mean? is the content of the file is multiple tickets with context for each one of them and you would like to create them as separate tickets in Jira, if so please provide a screenshot of your excel file with the name of columns you used.

in case not, and this excel actually having a template that you want your Jira tickets to follow that would be something different, it cannot be achieved by importing rather than working in Jira settings to set it up. to do so, also i would need to have more clarity about this template so i will be able to guide you better.

to respond to your specific question, Epic should be mapped to Issue Type.

Regards,

All comments

Antuan Sammak

Hi @Dominika Włodarczyk

Welcome to the Atlassian Community!

to respond to your specific question, Epic should be mapped to Issue Type.

Regards,

Dominika Włodarczyk

Hi @Antuan Sammak , thank you for such a prompt answer

Please see below names of my columns in excel file (saved now in csv format):

Zrzut ekranu 2023-12-19 114223.png

Below in the rows I have specific information for my company's projects and we would like to create some template, so it can be easily upload to Jira for new project.

What I managed to do is to save each column in separate CSV files and upload to jira one by one, but the subtasks are not connected to proper epic and it's quite time consuming for a large amount of data. Therefore I'm wondering if we can upload all data (epics, tasks, etc) from one file having their hierarchy saved.

Antuan Sammak

Hi @Dominika Włodarczyk

you can upload all in one shot except the subtasks, those will have to be in a separate batch.

first csv, columns should be like following: issue type / summary / description (these are the basic three columns) some additional ones: assignee / reporter / priority / label

first thing, each row in csv will represent one ticket.

now under column issue type, you can choose the type of the ticket epic/story/task. then write next to it under summary/description the data relevant to it.

go to Jira and hit on create button from top menu bar then a popup will open, on the top right corner of create popup you will see import issues, click on it and follow the steps its quite easy and straight forward.

once you have those tickets imported and created on Jira, prepare a new csv with same columns and add one more which is parent.

this csv will be for subtasks only, so the value under issue type column will be always subtask.

then next to each subtask/line you add the parent Jira ticket ID under parent column. last go to import issues as you did before and follow the steps.

please feel free to let me know in case you have any further questions.

Luka Hummel - codefortynine

Hi @Dominika Włodarczyk and welcome to the community 👋

Creating using the CSV import function for template issue hierarchies (Initiative → Epic → Task/Story → Subtask) can be quite finicky. Our app Deep Clone for Jira can help you replicate your template hierarchies really quickly and efficiently.

With our Epic/Tree Clone feature, you only need to have the template hierarchy set up once.

Deep%20Clone%20for%20Jira_Epic%20Tree%20Clone-20230728-084919

Timoti Sburv

You can structure your CSV file so that epics, main tasks, and subtasks are in the same file, using the Issue Type column to differentiate them. The Epic Name field should be used for epics, and tasks/subtasks should reference the epic via the Epic Link column.

If you need a more automated way to import structured CSV data while preserving these relationships, you can try Skyvia - (https://skyvia.com/data-integration/jira-csv-file-import-and-export)

Welcome!

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

Quick Links

Unanswered
Groups
Help

Find more posts tagged with

jira

cloud

jira-cloud