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

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


1 badge earned


Participate in fun challenges

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


Gift kudos to your peers

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


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!


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
Community Members
Community Events
Community Groups

Upgrade Paths need to be made more clear

As an Atlassian consultant, I spend a lot of time upgrading clients, some of whom have not upgraded Jira in years. One of my frustrations is that there is not a standard documentation page that lists the specific upgrade paths required for each version of Jira. I want to see a page with a simple table that indicates the required intermediate versions on my path to the latest Jira version. 

This should be a simple table that says "If you are on versions X.Y to X.Z, then you need to upgrade to A.B before upgrading further"

This would make it much easier to know which intermediate versions are required and are proven to work.

If this page exists, I can't seem to find it. 

1 comment

Hi @Derek Fields

I did a quick research on that matter. When you navigate to Plan your upgrade > 1. Determine your upgrade path > Show Jira Agile (or Core if applicable) on the following page (, you see a little table with the desired infos. It is not really detailed for each version, but it could help I guess. 

A more detailed table would be nice indeed. 

My best


Yes, indeed. That is the table that I am looking for. I think it should be upgraded to its own page, not hidden in a collapsible table. Thanks for pointing that out. 


Log in or Sign up to comment