I attach a reference to the Atlassian documentation describing how to set up a JIRA test environment.
Be sure to make a copy of your production database (with a different name) and connect it to the JIRA test environment.
We followed the steps and , after restoring everything from Prod (DB, Home flder) In Test server, We have noticed that the test environment has been taken the same license from PROD.
So we are worrying about where it got the link with PROD still now and will it impact anything.
Why the test environment license is not reflecting and what we have to do now here without making any change to PROD
Yes, it's as you say - it's a complete clone.
You do not have to worry, the production license for the test environment will not cause malfunction or interconnection of the production system. However, because of Atlassian licensing terms, a special license (free of charge) must be generated for the test environment.
The only problem can be in the application links if they are linked to other Atlassian applications. You need to delete them and connect them to the test environment.
Please note the following information (the information is written in the above procedure), particularly paragraphs 1., 4. and 5.
1. Modify the instance colors. See Configuring the look and feel of your JIRA applications. This is a good practice for users to identify that they're on the staging server.
2. Modify the instance base URL. See Configuring JIRA options and change the Instance URL to the staging URL.
3. Consider the URL whitelist. You may wish to change some of the approved URLs. See Configuring the whitelist.
5. Reconfigure applinks. If you are connecting to other servers via applinks, you'll need to change the server ID for those instances.
If you leave applinks in place, it's possible to have your production instance point back to the staging server, if a link is generated.
For now can we use the First test instance evaluation license key itself.?
If we can use it,
can we copy and paste the key over the test instance now and will it update in the test db tables.
Will it make any problem with the PRod instance.
(Hope, as the Test jira instance is linked to only TEST DB and revovng and putting bevaluation license in Test environment instance wont make any issue in PROD.)
For the time being , can we do this and later once we get the developer license of PROD, shall we replace the evaluation license with the Developer One ?
If you have a purchased license for production use, you have the option of generating a developer license yourself. Unfortunately, no one else can do it. Atlassian account should be automatically set up for the person who ordered the license (your technical contact). The only one has access to generating a developer license. You can still try writing to the Atlassian support question.
Please look into the JIRA administration -> System -> System info. There you will find the URL and the name of the connected database (verify that the test JIRA is connected to the correct test DB).
In the test environment, you can give a license key for the trial version (but if you leave the production license key there - is no danger, it's not right under the license terms). There is no need to update any tables in DB, just insert the license key in the JIRA -> Applications -> Versions & licenses.
We have migrated all our applications, Crowd, Jira, Bitbucket, Confluence to Test environment from Prod Servers.(By application data and DB data store to Test environment)
But , The application integration to Test Crowd and between Test applications how can make to Test Configuration for these applications, without affecting PROD
1)Test Crowd Should authenticate all test environemnt applications (Currently test crowd containing map with Prod application IP Addresses)
2)How The integration Between These applications in test environment can be replaced to Test application integration by removing PROD links
Since Production Data are copied and DB are restored, Now test applications will be having old trace with the production instances. How to revert it with test instances and what are the files need to be edited for enabling the integration
1) In the Crowd setting, you need to customize the configuration itself for specific applications (setting Remote addresses for test servers or creating a special test group with special users, etc.). Please look at the Crowd documentation Crowd Administration Guide
2) Just delete the current application links and re-create them for the test environment. All Atlassian applications will then only communicate with the test environment.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Can a new-to-agile team survive and thrive in a non-agile culture? If so, what advice would you give to those trying to be agile in a non-agile culture? What's the key(s) to success? Share your thoug...
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