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

CSV Import and Mapping Values for Epics

Brad Rutledge

I have been preparing and testing the import of existing issues held in another application into Jira. Last Thursday I was able to import a group of Epics with Name and Summary and create these in Jira. I the then mapped the corresponding field from my source data to the Epic Name. This worked and all the data was pulled into the Jira issues including the Epic Name the issues was linked to.

I had some other tweaks that I needed to do to the data to optimise the import and used the same configuration file with a couple of edits unrelated to the Epic name and when did another import test yesterday the Epic names did not populate. I have no idea why!

I am hoping someone can help me solve this puzzle.

Thanks,

Accepted answers

Ste Wright

Hi @Brad Rutledge

As long as the field is on the CSV file, the Issue Type is listed as Epic, and it's mapped in the import, it should work.

Are all those parameters in place?

Ste

All comments

Ste Wright

Hi @Brad Rutledge

As long as the field is on the CSV file, the Issue Type is listed as Epic, and it's mapped in the import, it should work.

Are all those parameters in place?

Ste

Brad Rutledge

Thanks Stephen. To clarify I have mass loaded the Epic's using the CSV import function and am now trying to add the Epic Name to the Issue when these are migrated as a Story. In my Story CSV file I have a column with the call Epic Name and column is mapped to the corresponding field in the Story which with my version is in French Lien d'epopee. The issue is the field is not mapping when I import and is blank. I had it working in a previous test but now it is not.

Ste Wright

Hi @Brad Rutledge

Epic Name isn't a field at Story level - are you trying to add the Epic Link (i.e the parent) to each Story you're importing?

If yes, you'll need to map the Epic issue keys to the Epic Link field, which should then work

Ste

Brad Rutledge

Thanks @Ste Wright you are spot on. I realised this morning when I was prepping my final import file that I was mapping to Epic Name rather than the Epic Link.

Welcome!

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

Quick Links

Find more posts tagged with

jira-software

unknown-hosting-type