Why can I not import issues into a new project that were exported from the same Jira instance?

Question

The format and names of the Jira columns (not custom fields) don't match up for some reason.  Why would that be?  Using CSV as export/import format.  The structure of the project exported from is identical to the project being imported into but that map fails in multiple places (e.g., creator, created, issue type.)

ksawyer · Answer

The proposition is relatively simple.  We are trying to directly import an export from the same Jira instance.  The export and import simply seem largely misaligned.  Not sure why.  We are trying to split one repository for 3 clients in a combined project into 3 repositories for ongoing support.  No customization across these repositories.

Next attempt will be to simply export 1 record and import it back into the same repository and see what happens.  Feels like it should be straight-forward.

As to mapping, I only see about 6-10 Jira fields to map on import from either tool.  Seems like there should be many more than that.

Ste Wright · Answer

Hi @ksawyer

It depends on the field.

Issue Type and Date Created should both be there in the Admin External System Import - these are available fields.

Creator however isn't, see JRASERVER-62308

This is expected and by design. The issue creator is always set to the logged in user who actually performed the "issue create" operation (in this scenario via import) and should be immutable.

There is a suggested workaround in that ticket - see this comment.

Ste

Daniel Ebers · Answer

I have a feeling this could caused by the delimiters used.
From the description the fields are not "splitted" correctly from each other unless there is something really strange going on.

Normally CSV export/import works very well and is a recommended way for many cases.