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 can I link stories and epics using Jira Cloud's csv import?

Alexa Aranjo

I am trying to "import issues from CSV" on Jira Cloud. I am able to define "Issue Type" as Epic or Story, but I am not able to define an Epic Link between a Story and an Epic.

Has anyone successfully linked an Epic and Story through csv import on Jira Cloud?

--------------------------------------------------------------------------------------

Additionally, "Start date" is coming in as a custom field, rather than a Jira field. Is start date not supported on csv import?

Separately, does Jira Cloud Roadmap only support displaying Epics?

Accepted answers

Petter Gonçalves

Hello Alexa,

Just to better understand your request, are you trying to create a new Story and link it to a new Epic OR an existing Story to an existing Epic OR an existing Story to a new Epic OR a new Story for an existing Epic?

Two options above can be done by configuring a column for the field Epic Link and map the Epic Issuekey as a value for it:

- Add an existing Story to an existing Epic:

You must re-import your Existing story using the exact same field values (You can even export the story and use it as a template to ensure everything is properly configured) and only add the field Epic Link:

Assignee, summary, description, created date, Epic Link
user, test summary, description of the issue, 18/sep/2018, TESTEPIC-1

P.S: unmapped fields will remain with the same value, so you only need to map the required fields for the import of the issue.

- Add a new Story for an existing Epic:

The same process of the first option, however, you will need to map all the fields you want, together with the Epic Link

Regarding your question on the Start Date field, I believe that this is indeed a Custom field, Alexa. The name of the date field created by JIRA that map the creation of the issue is called Created date.

Regarding your question about Roadmap, this is a new feature of JIRA, so I'm not very updated to its functionalities. I would recommend you to open a new question on the community for it, so the analyst and customers that are updated to this feature can better visualize this question.

All comments

Petter Gonçalves

Hello Alexa,

Two options above can be done by configuring a column for the field Epic Link and map the Epic Issuekey as a value for it:

- Add an existing Story to an existing Epic:

Assignee, summary, description, created date, Epic Link
user, test summary, description of the issue, 18/sep/2018, TESTEPIC-1

P.S: unmapped fields will remain with the same value, so you only need to map the required fields for the import of the issue.

- Add a new Story for an existing Epic:

The same process of the first option, however, you will need to map all the fields you want, together with the Epic Link

Alexa Aranjo

Thanks for the reply - I was able to link stories to an epic by adding the custom field Epic Link. The main issue was that I didn't have permission to configure custom fields on screens, but my site admin was able to grant access.

Petter Gonçalves

I'm glad to know your issue is solved, Alexa.

Have a nice day.

unknown

Hello,

I would like to follow up on the question above. Does that mean that it is not possible to link a NEW Story with a NEW Epic while doing a CSV Import?

Thanks.

Petter Gonçalves

Hello Martin,

Actually, you can link both new Stories and Epics in a single CSV import, by simply specify Epic Link mapping in your stories,

Example:

Issue Type,Epic Name,Summary        ,Epic Link
Epic      ,  my-epic,Build a car    ,
Story     ,         ,Build an engine,  my-epic
Story     ,         ,Buy some tires ,  my-epic

The example above will create an epic and link stories to that epic.

P.S: I didn't mention it in my first answer because I got the impression that Alexa was not asking for this specific feature, although I ask a question to make sure about it.

Let me know if this information helps.

unknown

Hello Goncalves,

I have tried this before. I get the following message:

unknown

We are using the Cloud Version of JIRA.

Welcome!

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

Quick Links

Find more posts tagged with

csv

jira

cloud

jira-cloud

import

issue-link

roadmap