Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

change from test environment to production environment (JSM - Data Center Version)


We are investigating the possibility of using Jira Service Management in the Data Center version.

We have a question regarding deployment.
How does the change from test environment to production environment work on system level (Please show technical procedure / Are there any best practices for JIRA instances or documentation links here?)

Thanks in advance

2 answers

1 vote
Andrew Laden
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
May 12, 2023

Built in Jira does not really have great tooling for doing a promotion from test to prod type of workflow. Because everything is stored in the database, and certain key pieces (like custom field ID's workflow ids etc) are set at runtime. even if you clone your production database to create test, it will quickly become out of sync.

There are a few Apps that can help. Configuration manager for jira is a popular one.

If you have a basic installation, it should work ok, But the more apps and other odd customization that you do, the more likely you will need to manually adjust the import, or it not work. 

Other then that, the answer is really just document the changes you make in dev, and follow your documentation to apply to prod.

I have a similar JSM project on my prod. Instance. If I want to test something I build it there and if it’s finished I change the project and screens and something to my main project. We have 2 instances but it’s really bad to out of the box to copy or import and export things from JSM to another especially services from customer portal.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events