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.
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 email@example.com if you are interested.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Hey Atlassian Community! Today we are launching a bunch of customer stories about the amazing work teams, like Dropbox and Twilio, are doing with Jira. You can check out the stories here. The thi...
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!
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