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.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Clone production and delete all the projects.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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 must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You do it manually, applying the changes you need. Or find/write something to transfer it for you, like the Botron software.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.