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.
Hi Everyone
I am working with a customer in a Jira 7.5.0 Setup with Portfolio 2.6.1 plugin. When we try to create a plan or display plan, system comes back with a message "Bummer, something has gone terribly wrong", suggesting to refresh the page (didn't work) or contact Administrator or Atlassian Support providing some kind of frontend stacktrace.
The stacktrace shows the following:
As you can see in the picture, there seems to be an issue with jpo-wr-page-plan-scripts.js script. I did some google search and i was unable to find this specific issue anywhere, however i have found relatable issues like.
https://community.atlassian.com/t5/Portfolio-for-Jira-questions/Error-on-some-Chrome-versions-Bummer-Something-has-gone-terribly/qaq-p/630324
https://jira.atlassian.com/browse/JPOCLOUD-1998
https://jira.atlassian.com/browse/JPOCLOUD-1956
I have already tried clearing cache, changing locale, with no luck. I am suspecting that system is trying to access web to locate some resource, however this install is not able to reach internet.
Need some help in order to solve this problem.
Best Regards
Rodrigo Valdés
Hi @Rodrigo Valdés,
I would first suggest trying to update Portfolio to its latest version to see if that solves the problem.
If that doesn't help it would be good to reach out to Support here: https://support.atlassian.com/contact
Let me know how that goes.
Cheers,
Thomas
Hey Thomas
Thank you very much for your help. I will try to update of the plugin as you suggest, and i'll let you know if that works.
Best Regards
Rodrigo Valdés
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
We updated the plugin up to 2.11.0 and the exact same issue happens. Think is time to open an Atlassian Support ticket.
Thanks for your help.
Best Regards
Rodrigo Valdés
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.