Best practice for Jira Cloud configuration management

[Peter M]

Hello community,

we plan to use Jira Cloud in our non-profit for project management. While we are IT professionals with experience with other products, we are still learning Jira, hence these questions.

We will have 3 JIRA instances (as sites) for dev, test and prod.

We would very much prefer to store the configuration in a text file, so that it can be checked into a git repo. Then, as soon as the configuration is ready to be tested/rolled out, it will be deployed the downstream environments.

Is something like this possible? What would be the best practice to manage different JIRA environments, please?

(The holy grail would be full Terraform support, but this is not the case afaik).

Thanks a lot for any hints

Peter

[Vish Reddy _Revyz_]

Hi @Peter M 

We are building some features in our Revyz Jira Backup & Restore app which are close to what you are calling out. These features are not yet published, but would be happy to share more details if interested. We want to enable movement of config data across sites seamlessly.

If interested please send an email to vish@revyz.io and we can coordinate a demo for you

Thank you

Vish

[Peter M]

Thanks Vish, I will reach out to you per email.

Peter

[Nic Brough -Adaptavist-]

Welcome to the Atlassian Community!

Jira does not have any configuration settings that can be exported and reused, beyond taking a full backup of everything, which can be imported into another empty Jira.

You need to be looking at tools that have been built to enable project and system configuration to be moved between systems - Configuration Manager and Project Configurator are the two I've worked with in the past.

[Peter M]

Nic, thanks a lot for the hints, we will give the two tools a try.

All the best!