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

Your Points Tracker
  • 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
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?
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

How to Implement Jira Server Configuration Management?

Jira Software Server 8.5.1
Jira Service Desk Server 4.5.1

What is the best way to handle change/configuration management for a Jira server (both service desk/service management and software)? Is there any way to get around tedious and error-prone screen by screen comparisons with mouse clicking?

Our goal is to setup a blue/green deployment environment and then have a development server behind that. I know we can use the full site XML backup/restore feature (in combination with the data directory backups for attachments, etc.). That is great for taking the latest production instance and replicating it downstream to refresh the development and test servers. However, since it wipes out existing issues, we cannot use it to apply changes upstream (from test to production). This means we'd have to apply all of those changes manually. Atlassian support has indicated they have no native way to handle changes in an organized way.

There must be some way to solve this problem. If it was possible to create a backup of just the issues without the configuration changes, then it would follow we could backup production issues, then apply the full XML backup from test to production, and then apply the issue backup to production to restore the issues. But I haven't found any way to backup just issues.

Any ideas or experience doing this?

1 answer

0 votes

So here I would say time to use docker. 

Correctly, wrap your configs into docker compose files OR set your configs into git (server.xml, 

Also, I would recommend you look into that one


I would recommend you start from proper documentation of upgrades, automate your steps via ansible or other tool, include that thing into cvs.

And then add into CI. 

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Marketplace Apps & Integrations

Staying organized with Jira: best practices for a better project management

Project managers know this problem: A “mountain of work” lays in front of you, and you don’t know how and where to tackle them. Different to-dos lie ahead, but just one task after the other can be ha...

153 views 2 1
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