Why isn't the active sprint board loading?

[David Trapp]

The active sprint page and backlog pages are not displaying.  I can still view the issues via the "Issues" tab, but when I click on the "Active sprint", the sidebar and sprint description load, but the board doesn't display.  When I select the "Backlog" page the page, same thing happens. I've logged out and done a hard refresh and doesn't change. 

[John Funk]

Hi David,

If you are using the Redux Devtools extension for your browser, disable that and see if the cards appear. 

[David Trapp]

Hey John,

Thanks for the suggestion, and that may have been what fixed it.

I say may, as after reading this, I opened the extensions and disabled the Redux Devtools extension, and then opened the Jira issues page (which had always been loading correctly). Then in the spirit of testing, I decided to see if the problem was still present, so I turned the extension back on and opened the active sprint page, which loaded correctly this morning. Not sure if resetting the Redux Devtools corrected it, or something corrected over the weekend, but problem is fixed now.  

Thanks for the help,

David

[John Funk]

I know they were to be rolling out a fix. Glad you are up and running again.  :-)

[Ruby Yan]

Hi @John Funk ,  I am facing the same issue. 
My backlog and active sprint are not loaded. but I am able to visit the other functions normally.
Preivously The issue only exists to one of my project. after I cleared cookie and cache. Another project working fine previously have the same issue now.
I didn't have redux extension installed on my browser.
Able to load in Incognito mode.

[Ruby Yan]

Get some apis error

[Jack Brickey]

Is this occurring for all users? Have you attempted to view the sprint on a different browser or cleared your cache on the current browser?

[David Trapp]

Hey Jack,

Was just occurring for me and I was able to view it on Microsoft edge, but not in Chrome. I tried clearing the cache on Chrome and still had the same issue.  But as of this morning, the problem is resolved.

Thanks again for the support,

David