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
Next: Root
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
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hello All,
I would really appreciate your support for the following topic.
I need to upgrade current Jira Portfolio version (2.18.0) to version 3.0.0 in a "server" Jira Software instance (version 7.12.3), and I'd like to execute the upgrade by myself through the "Manage Apps" page.
This is the first time I use this Administration section to perform add-ons upgrade, could you please share your experience in similar upgrades and any tips that might help me?
I'd like to know something about:
- (any) pre-conditions that must be accomplished before upgrading to Portfolio 3.0.0 (assuming that i don't have any "Classic Plan" to migrate)
- time required for the upgrade of Portfolio (e.g. minutes. hours, etc.?)
- impacts (if any) on users' activities during the upgrade (e.g. does Jira instance become slower?)
- any unexpected issues you faced during/after the upgrade to Portfolio 3.0.0
Thanks All for your support
Thanks Raathi, I used "Manage Apps" proficiently to update Portfolio and also other installed plugins.
Everything went well, no issues/errors found.
At the same time I also upgraded Jira from 7.12.3 to 7.13.1 and then to 7.13.3 without issues, just waiting for re-indexing to complete to retrieve performances.
Best REgards