Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal


  • Give kudos
  • Received
  • Given


  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

How restore the production database schema but not the issues into UAT

I want to be able to import everything via the XML export/import process from production to UAT. But without the issues.

Ie - there will be a Jira system that replicates production in terms of workflows, projects, custom fields, structures, minus the issues.

How do I edit the XML files to acheive that?


1 answer

1 vote

@Richard Lucas, out of the box  this isn't possible. If you want a system without any issues in it, there are  a couple of options. 


  1. Perform the restore and then use Bulk delete functions to delete the issues.
  2. Use a paid  add on such as Project Configurator for Jira or Configuration Manager for Jira. Each of these can transfer just the configurations, although there are some things that may not be transferred such as group memberships.



@Kian Stack Mumo Systems  Thanks for taking the time to reply - much appreciated. Its I'd hoped it would be an identifiable section(s) in the XML and just remove them.

Perhaps there is a way to do that through the XML, but I certainly don't know how!

Daniel Ebers Community Leader Nov 13, 2020

May I ask why the issues should be neglected?

I saw several requirements in the past:

  • we want to let a broad amount of admins to UAT, those should not see sensitive data - no matter what
  • we only want to allow sensitive data in protected live environments, not UAT (per decision / live environments protected better then UAT)
  • we want to minimize amount of data transported during replication as it has to be fast (fastest as possible)

Is is ok as per the requirement at all if the issues are deleted on destination? In some cases it might be prohibited to transport them (even encrypted) to delete them later from disk of UAT system.

Depending on the intention the approaches differ a bit - so if you could share the intention we might be able to advise further on how to go from there.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Jira

Announcing the waitlist for Jira Work Management

Hey there Cloud Community members! We’re excited to give you the first glimpse of the new home for business teams on Jira — Jira Work Management. Jira Work Management is the next generation of J...

637 views 10 16
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you