I've recently been tasked to upgrade our instance of JIRA and Crowd as I currently can't access the Crowd Portal due to the license being expired. I have then tried to enter a new key but it doesn't seem to like it. I believe the key is for a higher version.
My current environment consists of:
I have tried reading the Crowd Upgrade documentation but can't seem to find the recommended upgrade path for the latest version (Server 3.2)
What I'd like to know is do I upgrade JIRA first or Crowd?
If I upgrade Jira or Crowd first would it break the other functionality of the other? (Eg. Can I upgrade one first and then next week upgrade the other without any downtime?)
If anyone can provide me with a general guide on this I'd really appreciate your help.
Typically an Crowd upgrade is pretty smooth. For every upgrade it is good to make a test upgrade on test environment. Thanks to that you do not need to worry much. You simply follow upgrade procedure and check how it does. That is my recommendation.
Overall for every upgrade you need to read all release notes for all version starting from 2.8. I do not remember any specific upgrade path. Upgrade directly to the latest version should be fine. If you are afraid you can make an upgrade to 3.x and then to 3.2 (or latest) but definitely if you are using 7.3.x JIRA and Crowd is working now then it will be working later (after upgrade to the latest version). I think there should be no problem with upgrading Crowd first and then doing JIRA a week later.
This approach requires you to have the JIRA administrative rights. The main aim of this article is to help you achieve an organized, easy-to-maintain workflows in your JIRA instance thereby, reducin...
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