We are setting up a new instance of jira to replace our old system. The old system will be used as a development environment. How can I easily migrate projects (with associated config and issues if needed) to the new instance?

[Dave Scheet]

We have a current system that is running on a small development server.  We are in the process of standing up a new "production" quality server to run our JIRA system from.  We want to use the current system as a development environment so that we can test workflow changes and updates prior to putting them into production.  How can I easily migrate all of the config and issues from the old to the new.  And then going forward, how can I publish config changes to production once they have been tested.

Also, our current system uses JIRA's internal directory, but we want the new system to use Active Directory.  Is there an easy way to map users so that historical information is not lost.

We are not opposed to purchasing plugins to accomplish these tasks.

[Peter T]

Hi Dave,

Configuration Manager for JIRA add-on provides features to automate the process of moving configuration changes between JIRA instances and thus implementing Dev- Stage-Production environment for deploying JIRA changes. Using different directories for user management works great with our add-on.

We will be happy to give you a demo. Please drop us an email at sales@botronsoft.com if you are interested.

Cheers,
Peter

[Nic Brough -Adaptavist-]

I always reach for the Botron Configurator addon for moving configs around