How to deploy JIRA changes?

[Marco Nowak]

We established a deployment process for our JIRA changes (workflow changes, new custom fields, scheme changes etc). We do this at our test environment and once a month we do these changes on production all manually again.

Is there a better way to somekind of "export" changes from one instance and "import" it to another instead of doing all the work twice?

[Diego Baeza · Accepted solution]

Hello!

Yes, you can check this guide to 'promote configuration changes from staging to production'.

https://confluence.atlassian.com/adminjiraserver072/promoting-configuration-changes-from-staging-to-production-895916373.html

Let us know if this cover your needs.

Thanks!

[Joe Pitt · Accepted solution]

There really isn't a good way to do this. My approach was to create mirror projects that only I could see and create new workflows, fields, screens, schemes, etc. and apply them to the mirror project. After I'm happy with those I apply them to the real projects. I use version numbers for updated workflows, screens, etc. Since everything is in the same JIRA instance there is no problem moving them. I do have a development instance for testing plugins and new versions of JIRA. 

[Marco Nowak]

Thanks so far. But as I understand, I can only snapshot the complete instance or whole projects.

Isn´t there a way for workflows so that these can be exported and imported?

[Nic Brough -Adaptavist-]

Project Configurator can do full or partial transfer of config, including workflows.

[David Mayer]

Configuration Manager from Botron is what I use; otherwise you will have to spend a lot of manual time doing the same changes in Prod from Test or Dev.

https://marketplace.atlassian.com/apps/1211611/configuration-manager-for-jira