Best practices for transferring configuration between JIRAs

David Toussaint [Communardo]

Hi folks,

just now I came across a situation where I'm not sure of what is the best approach. So I wanted to ask you guys how you are handling this. Here we go:

We have three (!) JIRA systems running, on productive system, one test system and one development system. Usually for any major configuration changes we do the following:

1. "develop" settings and configuration that words on, done on development system
2. document this
3. ask our admins to use the documentation in order to apply the modifications to configure the test environment as the documentation says (two purposes: check the validity of the documentation and educate our admins)
4. check the test environment if all was configured correctly, (let other users test this)
5. modify the documentation and/or settings, if needed
6. ask our admins to use the documentation in order to apply the modifications to configure the productive environment as the documentation says
7. test on production environment if anything is missing
8. being done.

In order for this to work out the three systems are basically identical, settings are "synced" (manually, beloved admins) every now and then. There may be minor inconsistency but that should rather be an exemption.

Now I have configured a super complex workflow and everyone is happy and pushing hard for it to go live in the production system. So I thought I'd be clever, configuring screens, issue types and fields, installing needed plugins (it's all done already) and then only export the workflows as XML and reimport it on the productive system.

NOPE.

While doing this I just learned that all status' and screens and steps and stuff is called by its ID in the XML. While I can imagine possible backgrounds of this it basically means I have no chance (ok, 0,001% chance maybe) of using this export/import interface for transferring the workflow as the is a 99,999% chance of either a status, screen or step is having a different ID in one of the systems.

Is there any way you guys cope with such scenarios?

Oh, in case someone is suggesting the workflow sharing plugin, to me this thing is a complete mess. Inserts new statuses (bad mapping), cannot handle special characters (ä, ö, ü, ß - I’m in Germany...) and so on. Tried this already. I'm on JIRA 5.0.6 (both systems)

Thanks a lot, let’s have a fruitful discussion

David

abed

Hi

for the Workflows/screens changes i usually apply it on the production server and test it on a seperate jira project

if every thing was ok i apply it back to the rest of the projects

i only use the test system when planning upgrade or instllation new plugins

unfortunately in your case you need to create the screens, statuses and workflow again on the production server

or create the statuses/screens in the same order when you create them on the test server, the IDs are incremental, check them from the test site, then do the workflow import (it's gonna take the same time though "creating them from scratch" :P)

regards