nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

JIRA Development is way behind the production

Harish Tuccapuram

JIRA Dev is way behind, the data is not in sync with production.

I would like to replicate the production instance to Dev Instance for users to test and play around what is the best practice to do ?

Thanks

Accepted answers

All comments

Alexis Robert

Hi @Harish Tuccapuram,

the quickest way, if both instances are on the same version, would be to simply dump the production database and import it into your test database instance.

You can also simply use the native Jira export and import feature to copy your production content to the Dev one.

Let me know if this helps,

--Alexis

Harish Tuccapuram

Thanks @Alexis Robert

I would like to follow the second approach i will export the production XML and will dump into the dev do i need to keep anything in mind before doing that?

i know this might be dump to ask but wanted to check there should be no talking with Production instance that what i wanted to do to be on a safer side.

Vickey Palzor Lepcha

Some of your Production configurations could reflect in your DEV instance - that you can verify and change if needed.

- LDAP Config - just verify

-BASE url

-Internal Directory Users

-Application Links

Vickey Palzor Lepcha

I'd say just go for a random check of all your JIRA DEV info just to ensure that nothing points to Production Data.

The xml import is pretty safe - I have done it quite a lot of times.

But yes, depending on your Production Data - it could take time. Mine sometimes take 2 hours to complete.

Harish Tuccapuram

Everything the below mentioned to be done after the import on the Dev instance or once the XML is exported from prod do i need to change that in the XML ?