We have a hosted Jira which very old (v2.3.1) How do we estimate the work involved in migrating it to OnDemand? E.g. is there a check list of things that need to be done?
To go from 2.3.1 you are talking at least 2 upgrades. You can't go straight there. I would talk to the support folks to find out if they will do that or you have to before hand.
You are talking having to go from 2.3 to 2.7. Then 2.7 to 3.1 (if I remember correctly). From there you should be able to go from 3.1 to 5.2 but you'll need to check and see what the OnDemand instance will be running.
If you are using AD/LDAP auth, there are SIGNIFICANT changes that will complicate the upgrade and you'll want to spend a good amount of time testing by having actual users test.
Significant changes to plugins, but that may or may not impact you. Some folks have kept their environments pretty vanilla, others not so much. If you are in the latter camp, some set of plugins will likely have gone away and you'll either have to be ok losing the functionality or roll your own.
You'll want to do a dry run on things. There are a lot of changes, depending on your data set, configuration and usage, it may be worth your time to do several dry runs and see.
It will be a new system for most users because things will be very very different.
A dry run will give you a sense of actual time to perform the upgrade. Plan your support around that time. More dry runs will give you more accuracy in timing.
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
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
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs