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

export epics and stories in a csv

JEAN MARC PUJOL

Hi everyone,

I need to export all my backlog in a csv. Versions, Epics and stories (with the link between them).

Exporting stories works fine. But how can I export the epics? I don't want to loose the link between epics and stories.

Thanks for your help.

Jean-Marc

Accepted answers

Petter Gonçalves

Hello Everyone,

A quick update to this question:

Today, it is possible to properly export issues and their related epics (including the link between them) to a CSV file in Jira Cloud and Server applications.

For Jira Classic projects (Software or Service desk), these would be the steps:

Click in the filter drop-down at the top of the page > Advanced Search

In the Issue navigator page, type a JQL query to return all the Epics and related issues you want to export. P.S: You can use the "Epic Link" field to select the issues related to a specific Epic

If you want to export specific fields from your issues, including the Epic link:

At the right side of the search bar, select "list view"

Then, add the column "Epic Link" > Click in Export > Select "Export Excel CSV (Current fields)"

If you want to export all fields from your issues, including the Epic link, Click in Export > Select "Export Excel CSV (All fields)".

In both options above, the relation between Epics and child issues will be informed by the "Epic Link" column.

For Next-gen projects (available on Jira Cloud), the same steps above can be followed, however, using the "Parent" field/column to export the Epic relation.

Best regards,

Petter Gonçalves - Atlassian Support

All comments

david_fsrxhm

Hello Jean-Marc, with the default Jira export to CSV you can't export what you need.

You will need to use a third-party app, one that fits you is Exporter: https://marketplace.atlassian.com/plugins/com.deiser.jira.exporter/server/overview

It allows you to export to CSV no only Stories and epics but their link, issue comments, and transitions. In case of Server instances, also Attachments.

I hope it helps,

Cheers

JEAN MARC PUJOL

Thanks David for your quick answer.

Basically I need to migrate the whole product backlog of a project running on a JIRA instance hosted on Amazon, to another project running on another JIRA instance .

CSV file is the only way I 've found to do it. I'll have a look at Exporter.

david_fsrxhm

Yes, the CSV export is made especially for migrations.

Good luck the migration, btw!

Aron Gombas _Midori_

You can take this path:

Use the Better Excel Plugin to export epics and stories and whatever info is needed to an Excel file
Open that in Excel
Polish the data if necessary (renaming items, etc.)
Then export that to a CSV file

I am a developer working on this app, and we have several users who took this path.

Petter Gonçalves

Hello Everyone,

A quick update to this question:

Today, it is possible to properly export issues and their related epics (including the link between them) to a CSV file in Jira Cloud and Server applications.

For Jira Classic projects (Software or Service desk), these would be the steps:

Click in the filter drop-down at the top of the page > Advanced Search

In the Issue navigator page, type a JQL query to return all the Epics and related issues you want to export. P.S: You can use the "Epic Link" field to select the issues related to a specific Epic

If you want to export specific fields from your issues, including the Epic link:

At the right side of the search bar, select "list view"

Then, add the column "Epic Link" > Click in Export > Select "Export Excel CSV (Current fields)"

If you want to export all fields from your issues, including the Epic link, Click in Export > Select "Export Excel CSV (All fields)".

In both options above, the relation between Epics and child issues will be informed by the "Epic Link" column.

For Next-gen projects (available on Jira Cloud), the same steps above can be followed, however, using the "Parent" field/column to export the Epic relation.

Best regards,

Petter Gonçalves - Atlassian Support

Nicole Peters_mh66jh

Could you provide an example of the JQL query?

Petter Gonçalves

Hello @Nicole Peters,

The structure of the JQL query depends on what issues you want to export.

To give you a practical example, let's suppose you want to export all Epics together with its child issues from the project "ABC". This would be the JQL query:

project = abc and (issuetype = Epic or "Epic Link" is not empty)

Let us know if this information helps.

Anita Hütter

Hello everyone!

In my case I cant find the issues that has been created in the epics instead I added the Epic links. The epics has been exported and imported but without the lists of issues in epic and Issue Links.

In the log of the Importer you can find the errormessage:

Cannot add value [ [XXX] ] to CustomField Epic Link in Issue with summary 'YYYY'. Probably value was in incorrect format

The link comes from the export before.

It would be very nice is you can give me any suggestions.

Kind regards

rcdpanjaitan

Hello

@Petter Gonçalves

I already include the Epic Link in the query, but when I exported to csv, it only return the issue id of the Epic.. any idea what to do?

thank you

Welcome!

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

Quick Links

Find more posts tagged with

jira

atl-gruland