How do you move changes from your development environment to your production environment?

[Sarah Kladstrup]

We have a lot of customization and plugins in our Jira instance, including scripts with Script Runner, Behaviours, and other custom fields.

Project Configurator doesn't seem to handle moving any of these customizations.

How do other teams and companies move smoothly from one environment to the other? Right now, we're doing most changes manually in each instance (dev & prod). Isn't there a better way? What is said "better way"?

[JP _AC Bielefeld Leader_]

You're asking the Holy Grail question bothering not only you...

While Jira is amazing what you can do & achieve with it, it sucks on synchronizing a dev / test / stage / prod environment. Project Configurator is a first step, but it doesn't handle all the stuff...

Manual work at our company...

Best

JP

[Payne]

We use a pricey but really great add-on called Configuration Manager.

https://marketplace.atlassian.com/apps/1211611/configuration-manager-for-jira?hosting=server&tab=overview

[Sarah Kladstrup]

Does this handle Script Runner scripts and other add-on specific changes?

[Payne]

Yes, things such as ScriptRunner (and other add-on) validators, post functions, conditions, etc. Everything related to a project.

[Michael Bibby [Praecipio]]

We migrated a project from dev to our UAT environment that included script-runner objects, but were not migrated.  Is there a particular process that needs to done to ensure that the script-runner functionality is included in the migration?

[Sarah Kladstrup]

Re-reading some documentation, I've found this: "For changes such as creating new workflows (that require administrative access), ... Require end-users to document specific workflow or scheme setups, then repeat these steps in production*."

*emphasis mine

https://confluence.atlassian.com/adminjiraserver073/establishing-staging-server-environments-for-jira-applications-861253111.html?_ga=2.23164474.1477021775.1559854700-569567187.1554496979