However I am only responsible for only one of the projects and I onlly want one of them to be upgraded. So I'm thinking I will create a second production instance and upgrade that to 5.1.7 following the 4 steps above and delete all the projects that I'm not responsible for.
That will give me 55 projects on prod1 JIRA on version 3.6.2 and 1 project on prod2 JIRA on version 5.1.7
This is good but what happens when a second project on prod1 wants to be move to prod2 and be on a later version of JIRA.
I can't see how I export just one project from prod1 on v3.6.2 and import it into prod2 on v5.1.7 for 2 reasons:
Please advise how I can import the second project ?
The upgrade from 3.6.2 has to go through an interim stage of being upgraded to 4.X first. see this article: https://confluence.atlassian.com/display/JIRA051/Upgrading+JIRA+3.x+Data+to+JIRA+5.0
What you are proposing would probably work, but it would require a lot of work 3.6.2->4.4.4->5.1.7DEV->5.1.7PROD
Requires about 3 hops
This might be just as hard, but maybe you can manipulate the Jira 3.6.1 xml backup and only keep the project you want when you import into your temporary 4.4.4 instance.
I am not sure I would want to try to convert your 3.6.1 xml backup into a 5.1.7 xml file.
I just wanted to give a bit more background info. The version of JIRA running currently has grown organically over the years since installation in 2006 and has pretty much looked after itself since then. We now have 56 projectd and over 300 people set up in it but more or less no one in charge of the whole installation. People are siloed and work on their own projects. I feel it would require a lot of work to get everyone to upgrade at the same time. All projects are at different stages and getting people to come in on a Monday and start working on 5.1.7 might be a big task to make happen. Hence I wanted just to upgrade one or two projects at a time.
However the current procedure requires a stepping stone of exporting out of 3.6.2 in XML and importing into 4.4.4 then upgrading in situ the 4.4.4 db to 5.1.7. At that point you've lost your 4.4.4 swing database. So migrating one or two projects at a time is not repeatable as you lose your 4.4.4 version everytime you do an upgrade.
Does anyone have any further suggestions ?
I agree with Nic. Spreading out the migration, training and complaining for a long period of time is counterproductive.
Your version is already beyond Atlassian's end of life policy and it probably not wise to continue this way.
Even if you just upgrade to 4.4.X (end of life in early 2014) it will hopefully make the next upgrade alittle easier.
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