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 export JIRA from one instance to another without the actual data

William Wells1

Is there any way to export just the issue types and possibly customized fields without exporting any of the user entered data for JIRA? I have to setup a new JIRA instance on a separate network for another team, to share the same setup, but without any of the information (i.e., HR might have personnel information that the recruiters don't need to see).

Accepted answers

William Wells1

Thanks for the reply Ramiro.

One option that I've come up with might be able to resolve this issue as a work around as well. When you perform an export from the original system, you can open the .zip file and modify the entity.xml file to remove all refrences to the issue_id lines. Save the file, re-zip it, then import the new .zip file into the awaiting system. I was able to import the issue types and schemes without any of the user entered data.

Another option is to export as usual, import into a fresh Jira installation, delete all Project, User, and Group entries from within JIRA, then perform an export. Take that new export and import it into the destination system.

These two approaches pretty much do the same thing, but one allows the application to perform the changes to the entity.xml file itself.

All comments

Ramiro P

Hi, I've investigated a little and found this. I'm afraid it's not posible, but there's a few workaround solutions. Hope this helps!

William Wells1

Thanks for the reply Ramiro.

These two approaches pretty much do the same thing, but one allows the application to perform the changes to the entity.xml file itself.

William Wells1

Thanks for the reply Ramiro.

These two approaches pretty much do the same thing, but one allows the application to perform the changes to the entity.xml file itself.

Ramiro P

In my opinion, I would recommend the second option because it would guarantee the data integrity. Is much safer. Have you already done one of the two options?

William Wells1

I have actually done the first one already with success. I am currently working on the second, but it will take me a little time to setup another test environment before I can try it out. I agree with you on the data integrity 100%, but in case that doesn't work I do feel that the 1st option is viable.

Ramiro P

I'm glad it worked! And this is a pretty interesting matter. Remember to mark your answer as correct in order to help the other users.