Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Upgrade from JIRA 7.3.4 and Crowd Version 2.7.2 to Current

Hi All,

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:

  • Ubuntu Linux (64-bit)
  • Atlassian JIRA (v7.3.4#73015-sha1:a262b34) 
  • Crowd Version: 2.7.2 (Build:#626 - 2014-05-13)
  • Operating System Linux 3.13.0-66-generic
  • OS Architecture amd64
  • Application Server Apache Tomcat/7.0.52
  • Servlet Version 3.0
  • Java Version 1.8.0_60

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.


1 answer

0 votes
Mirek Community Leader Jun 18, 2018

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.

Thanks Mirek,

I'll see if I can arrange for a backup and then have Crowd upgraded and see if it works.

AnnWorley Atlassian Team Jun 20, 2018

Hi there - Johnny, wanted to share this in case you did not find this doc with two upgrade methods described: Upgrading Crowd

Suggest an answer

Log in or Sign up to answer
Community showcase
Asked in Jira Service Management

JSM June ask me anything (AMA)

Hello Community members! We’re wrapping up the end of JSM June with an Ask Me Anything (AMA) with the Jira Service Management product team. This is your chance to ask all your ITSM questions to o...

233 views 12 14
View question

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you