We have multiple test instances that are replice of our Production Servers.
We normally keep restoring test instances with latest XML backups from production server for testing purposes.
When an XML backup is restored, it brings in all the data from production including its URL in general configuration.
And often times developers forget to change the URL and start testing on it.
So for example, if you open an open a new dashboard in new window with the middle button of mouse, it opens with the actual Production Server.
And often times this could lead to making test changes on Production server.
Could anyone tell if there's a way to enforce JIRA not to run when Base URL doesn't matches the actual url?
Lately, I've noticed that the warning also doesn't appear, telling you're accessing with incorrect URL.
But even without the warning is there a way to enforce JIRA doesn't run with incorrect URL?
Something like that would have to be done with a proxy. There is a communities post that deals with a very similar topic for Confluence titled Redirection to another confluence base url that you can start with.
Here is some additional documentation for re-directing:
I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...
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