Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,458,048
Community Members
 
Community Events
176
Community Groups

Is there a recommendation for upgrade order of Atlassian products?

I currently have these Atlassian products:

Crowd 2.11, Confluence 5.9.4, Jira 7.0.10 and Bitbucket 4.4.2. 

It is now time to upgrade, and the users want these versions:

Crowd 3.0.2,  Confluence 6.5.1, Jira 7.6.1 and Bitbucket 5.5.4

Is there a recommended order for upgrading these products? I assume I start with crowd, but I am not sure about any dependencies the other products might have. 

thanks for any helpful hints.

1 answer

1 vote
AnnWorley Atlassian Team Dec 11, 2017

We don't have an official recommendation but I am inclined as you are, to upgrade Crowd first, if everything depends on Crowd to authenticate. Crowd 3.1.1 has been released, do your users have a reason they would rather have Crowd 3.0.2?

I asked a Jira engineer about Jira and Bitbucket and there is no preference for the sequence of upgrading the two of them. From Confluence 5.9.4 to 6.5.1 is a major upgrade because Collaborative editing was introduced in Confluence 6.0.

I strongly recommend trying the upgrades in a test environment first to avoid surprises in Production. Mirror Production as much as possible, for example, if the applications in Production have application links between them, link the test apps the same way.

I hunted down some docs that should help you get started:

Crowd

Upgrading Crowd

Crowd 3.1 Release Notes (in case they want the latest)

Crowd 3.0 Release Notes

Bitbucket

Install or upgrade Bitbucket Server

Bitbucket Server 5.5 release notes

Jira

Upgrading JIRA applications

JIRA Software 7.6.x upgrade notes

Confluence

Confluence 6.5 Upgrade Notes

Upgrading Confluence

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events