Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Default jira configuration

Hi All,

I'm researching for an approach how to deal with default jira configuration. I have default jira configuration with all projects, workflows, fields, issue types, etc configured. I need to export all this already set details and to import them to brand new jira instance.

All ideas are welcome :) 

Thanks in advance

1 answer

Is it ok to replace all data in the new Jira instance? If so, I suggest you to

  1. dump DB with Jira data
  2. restore DB to NEW Jira instance database
  3. copy {jira-home}/data to {jira-home} in NEW Jira
  4. copy {jira-home}/plugins to {jira-home} in NEW Jira
  5. start your NEW Jira and do full reindex

You could use XML backup and restore process but as described here, it is better to use native DB backup and restore - https://confluence.atlassian.com/adminjiraserver/backing-up-data-938847673.html

It is ok everything to be replaced.

Your suggestion maybe will work for me.

I have only one concern about it. How to deal with some unique Jira properties such as Server ID which will be replaced as well?   

Good point, I'm checking on two environments, one environment is clone of another and these properties are same on both instances. We are using it as testing environments so this behaviour is OK for us, but if your environments are production env, it might be problem.

Solution could be to dump DB as SQL for both instances and replace particular parts of SQL with SQL from New instance, but it might be complicated :(

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Jira Service Management

JSM June Challenge #2: Share how your business teams became ITSM rockstars

For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...

298 views 9 7
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you