Creating a JIRA DEV environment from a JIRA TEST environment

Question

Hello,

We are trying to create a new DEV Environment from our current TEST environment in JIRA DC (single node) for the first time, but we are stumbling on some issues. We are using only JIRA JSM 5.12.26 application installed at this moment (no core, no software).

Does anyone have an answer to the issues below:

A.  Regarding the cloning of the TEST DB into a new DEV DB, please clarify few things for us:
- is schema JIRA_ITSM the only one used by application?
- are rowIDs used within our application?
I am asking all these details as the easiest way to copy test env into DEV env would be to use schema export/import method - but using rowIDs would be a stopper here.

B. regarding the cloning of the new server in AWS from TEST to DEV, the server volumes are encrypted as a security policy and don't know how to proceed with the cloning. Any advice?

C. regarding license: How do we get a new DEV license for the new JIRA DEV instance?

Thank you in advance!

Best regards,
Alexandra

Jayesh Raghuvanshi_qb6277 · Accepted Answer

@Alexandra Mihaela Apostol

Question C: Go to https://www.atlassian.com/purchase/my/ whenever you purchase license you get a developer license to use on Non-prod sites you can get those information there. If that license doesn't works no problem you can use prod license keys also it won't make any impact to your prod instance, we had 4 Non prod env, so we used to provide the prod license keys to all the environments

Question A:  Jira applications (including JSM) use a single database schema, but the default schema name might vary based on your DB setup. Typically, Jira uses one main schema for all application data. The schema name "JIRA_ITSM" could be your custom schema name for Jira Service Management data, but this is not a universal default.

You can get the schema details in dbconfig.xml file present in your Jira Home

Question B: You can create snapshots of the existing encrypted EBS volumes and then restore them to new volumes for the DEV server. Ensure the AWS keys and IAM roles have rights to manage encrypted volumes.

Your AWS admin will be able to help you for this. Only you need to move the Jira Shared-Home, rest Jira home and Jira Install can be created fresh, install the new tomcat and run it.

We also provide freelancing consultation in case you need assistance.

If you like the answer, Kindly accept it.

Thanks

Jayesh R