How to replicate a production jira to test jira leaving behind the data

We have a JIRA production server and we now want the same project to be replicated on a JIRA test server but we don't want all the issues(production data) created in the production to be imported in to our test machine.

How can we handle this scenario of import leaving behind the data.

1 answer

1 accepted

2 votes
Accepted answer

The standard approach to this is to clone production, then delete all the projects.

A newer, easier, approach is to Botron's project configurator - it can take a single piece of config, a swathe, or the whole lot and replicate it across systems.

is there any other approach than to depend on a third part plugin

Clone production and delete all the projects.

Nic, Thanks for the quick response. The above solution of cloning and deleting works fine if I want to move from production to dev server. But, if i have some changes in the development machine and I want that changes to go into production server without losing data(issues), what will be the solution for this? Thanks in advance!!

You do it manually, applying the changes you need. Or find/write something to transfer it for you, like the Botron software.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Jan 08, 2019 in Jira

How to Jira for designers

I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...

839 views 3 9
Read article

Atlassian User Groups

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

Find a group

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

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you