Nope, unless you are in a "clustered" mode (i.e. datacenter license), JIRA will not start if 2 instances are trying to access the same database.
But if you point a second installation of JIRA to your jira_db production, any changes in your JIRA test will affect your production database.
What you want to do is to duplicate your database (potentially on the same database server, but a different database, for example jira_db_test ) by dumping&importing your db from jira_db (prod), and have your test instance to point at this one
Hope it helps
Only if you really want to corrupt your data.
The whole point of a test environment is that it is isolated from your production environment so that you can sanity check behaviour before putting your production data at risk. Even within the limited circumstances where this is possible, it's a very bad idea.
Clone your database and point your test instance at the clone, instead. The first time something goes wrong, you'll be very glad that you did.
Hey Community mates! Claire here from the Software Product Marketing team. We all know software development changes rapidly, and it's often tough to keep up. But from our research, we've found the h...
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