We have grown into JIRA and now we are looking to formally set-up separate production and development sandbox environments. The challenge is confused by the fact that our current environment VM web server is accurately named "WebPrd" and the VM database server is named "DBDev01" which is misleading and problematic.
We are using JIRA 6.4.12, Linux 2.6.32, mySQL 5.5, Tomcat 7.0.55. We are relatively inexperienced with the application and are open to a simpler method or cautionary tales to share too.
Our high level plan is to create a new VM database server "DBPrd01", install mysql and restore a database backup to it. Next we would clone the current "WebPrd" and call the new VM server "WebDev". Afterward we hope to be able to edit the system configurations stored within a file in the /conf/ folder to make the correct logical connections between the web and database servers. Does anyone have a reference URL for instructions on how to do this?
I'd actually "migrate to another server", then drop the bits about turning off the old server. Just make a few tweaks to the new one (developer licence, turn off email, disconnect it from any production integrations)
Have a look through https://confluence.atlassian.com/jira/migrating-jira-to-another-server-151126305.html to get an idea of what you're looking at.
It does look a bit long winded and scary to new people, but it's actually mostly common sense.
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
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