You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
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:
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.
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 https://community.atlassian.com/t5/Portfolio-for-Jira-articles/Introducing-a-new-planning-experience-in-Portfolio-for-Jira/bc-p/977363#M44
To go though your cases:
Are you looking to use Cloud or Server going forward into the future?
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.