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
Hi @Calvin Senteza ,
I'm sorry you're experiencing this issue. Could you let me know what version of Portfolio for Jira you currently have installed, and also which browser/version/platform you're using?
Portfolio for Jira team
From the screenshot I can see that the page scripts have loaded, as the loading indicators are displaying. These continue to display while the scripts attempt to retrieve the backlog data for the plan, so there's either going to be an error retrieving the backlog, or an error processing the data that's returned.
I can't replicate this in a local environment with the versions you've outlined, so it may be that there is something specific to your Jira set up that's causing this to occur.
Have you upgraded Jira or Portfolio for Jira recently, or changed any settings for the projects the plan uses? Did this issue start occurring after a specific upgrade or settings change?
The owner of the plan did some incremental changes to the source to see if he could narrow down what might be causing the issue. He was able to confirm that if he removed the data source Board= "x". Once he removed this board, the plan started working well and saw the issue come back when the board was added as a data source. No specific upgrade changes as this was a new plan that caused the issue.
It's interesting that portfolio is not liking something about this particular JIRA board. Without being able to see log files or console errors, I'd be stabbing in the dark to work out what might be wrong here.
It might be helpful to compare this board configuration to other boards that are working correctly in portfolio. Is the board based on a project, or a filter? Does the project setup for this board differ to the project setup for other working boards?
We experienced the same behaviour.
In our case we don't use boards to add the scope. Instead we add full projects.
We added the hierarchy level "Feature/Initiative" and the cause was in the end a cyclic reference.
We had a feature that was linked to an epic that was linked to that feature.
Maybe this helps.