Always a fun question. It used to be "a manual slog" and "some scripting with bodges". But nowadays, I lean strongly towards a couple of options.
First, it depends on what you mean by "sync". You have 2 JIRA systems, with projects and issues in both.
If your 'sync' is issue to issue (so an issue in dev is commented/updated, and the same issue in prod needs to be updated), then you really want to look at K15t's Backbone product.
If your 'sync' is about the configuration you've been doing (i.e. you rig up a project in dev, with workflows, screens, fields and the rest, test it and decide "yes, we like this" and want to transfer the config to production), then, look to Botron's Configuration manager
Thanks for the reply. You've brought up some good points. I think we're leaning towards using the dev instance for testing then moving to prod, BUT the idea of keeping both instances mirrored/synced is appealing as well. I think for our purposes, if the Configuration manager can transfer all the work to the prod instance, then that would be a great safe guard and a truly better dev tool.
The thing about the k15t thing is that it is dynamic - I think it's more for the cases where you have say two organisations who want to collaborate, and they both have their own JIRA installations. Instead of having to argue about which one you should use, and going through all the "fun" of securing them so that people can only see the shared areas, Backbone lets you set up a project on both sides and just synchronise between them. It's still 2 projects on separate systems, but mirroring the data. You can do it as a flat 1:1 so they're identical, or you can pick and choose which bits you sync (dropping fields etc). You can even do it internally (one JIRA and two projects that sync!)
I suspect Conflguration Manager is better for you though. It's aimed at transferring config between systems, and it works well. You can define (and version) exports of one or many project configs, and once you've imported a project config, you know that the target project is now ideally set up to use JIRA's internal "project import" to draw in the issues if you want them.
One of the main use cases we wanted to target with Configuration Manager for JIRA was moving configuration from dev to prod in an automated way which also gives users complete confidence in the changes they are performing to their production systems. Drop me an email at email@example.com and we can organize an online demo for you where we can show you how Configuration Manager works and discuss your exact use case.
Your suggestion of these two products may have solved, for me, not just a handful but a bucket full of things I am working on. To wit:
Thanks for that.
Thanks for mentioning Backbone, Nic.
Nathan and Mike: We're holding two intro + demo webinars on the add-on this Wednesday, details and registration are here: https://www.k15t.com/blog/2016/06/backbone-issue-sync-for-jira-two-webinars-on-june-15th
For more info on the product right now: https://www.k15t.com/software/backbone-issue-sync
And we're always happy to answer questions directly: firstname.lastname@example.org
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG