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!


Testing Portfolio on both Cloud and Server and having two very different experiences

I'm trying to determine if we have a version or user problem or if the functionality between Portfolio for Cloud and Server are very different. 

I like the features I'm seeing in Portfolio for Server and I can't figure out how to replicate these on Cloud. Is it possible? Some of them are:

  1. The concept of a Program -- being able to have multiple plans roll up into a program and display the initiative level roadmap items on a single roadmap. 
  2. The "Roadmap" view of a Plan. On Server, I have three options: Roadmap, Teams, Releases. On Cloud I have: Scope, Team, Releases. Scope is similar, but the roadmap is created above the items that feed into it instead of aside them. The roadmap on cloud seems to be completely algorithm based while server seems to give the user some control.
  3. Review changes - in server, when I make changes that will impact JIRA, I see a "Review changes" button with a number of how many changes I made. I can accept or decline these before pushing the changes to JIRA.


Overall, the two seem to behave very differently for me and I can't figure out if the versions between both are just different or if it's an install problem.

1 answer

1 accepted

2 votes
Answer accepted
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Apr 03, 2019

Hey @Stephanie Willis ,

There are some changes between the Cloud and Server versions of Portfolio for Jira. This can happen as certain features are prioritised differently for different deployment options. For more on this see

To go though your cases:

  1. Programs is only available in the Server version.
  2. It looks like you have the 'new experience' feature enabled on your Server plan. Those differences you mentioned are correct. 
  3. In Cloud this can be found under the "Uncommitted changes" button.

Are you looking to use Cloud or Server going forward into the future? 



Thanks Sam! I don't want the roadmap to be based on an algorithm, I want something very low effort for the PMs on my team to make changes to. We are on Cloud right now but considering switching to Server for this feature.

Is there any update on a target release date for Portfolio 3.0 Cloud?  We are on Cloud and plan to remain there.


Are there any articles available for feature comparison between Portfolio server and cloud today?  I can't seem to find any and this is needed to manage the transition during our migration of Jira server to Jira Cloud.  Our users have raised questions during testing on the differences they encountered, and couldn't find the equivalent of the functions they have been used to in Portfolio 3 on Jira server.

E.g. lack of programs in Portfolio Cloud, planning interface looks different, no drag-and-drop interactivity in the timeline/schedule/roadmap, bulk actions not available in Cloud to update issues, filter options not available, etc.

For functionalities or features not available in Portfolio Cloud, are there workarounds available? Users have been used to these features in Portfolio 3, and this seems to be a downgrade for them when we migrate Jira to cloud.




Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events