Refreshing JIRA dev server with JIRA production server data


I am looking into updating our JIRA dev server with production data.

However, I want to be sure any plugins work I have done doesn't get over-written.

It would be ideal if the refresh only changed the issues in project and left everything else alone.

Is this possible? How do you guys create your dev servers?

My worry right now is taking a mysqldump and restoring it will lead to over-writing any expirements we are running in Dev. Any advice?

2 answers

1 accepted

0 votes
Accepted answer

We ended up creating a seperate JIRA staging server that is refreshed periodically, but no experiments are run on.

Our setup now resembles the one outlined in this document. It works out for the best.

We have a script that refreshes the db but also attempts to set the header color and update the LDAP config. For future reference so as to let users distinguish the different instances.

0 votes

You are spot on. If you do the full restore, any experiments you have been doing will be overwritten. If you just want to import the issues, you might want to look at doing a project import. But that will need the same plugin version etc even though the configurations can be different.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Jan 08, 2019 in Jira

How to Jira for designers

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 ...

1,098 views 4 9
Read article

Atlassian User Groups

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!

Find my local user group

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

Groups near you