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 replicate a production jira to test jira leaving behind the data

Raghavendra Rao Inala

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.

Accepted answers

Nic Brough -Adaptavist-

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.

All comments

Nic Brough -Adaptavist-

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.

Raghavendra Rao Inala

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

Nic Brough -Adaptavist-

Clone production and delete all the projects.

Raghavendra Rao Inala

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!!

Welcome!

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

Quick Links

Find more posts tagged with

jira

jira-administration