Highest Summary
Some users might be unable to temporarily see Jira sidebar in the new UI.
(Other problems may occur as dashboards loading blank and other areas of Jira)
Steps to Reproduce
- Not easily reproducible.
Note: This can happen for various reasons, the symptom is usually missing/blank areas in the new UI.
Expected results
The sidebar and other icons should render normally.
Actual result
The sidebar and other items loads blank
Workaround
Before, contacting support try the following possible workarounds:
- Using incognito mode may work for some cases.
- Opening the development console and going to the network tab marking the option "Disable cache" and refreshing the page.
- A different browser may also work.
![[Atlassian Service Operations JIRA]](/images/icons/generic_link_16.png "[Atlassian Service Operations JIRA]"){kind=icon}
[JRACLOUD-68518] Some users may be unable to see the left sidebar in Jira new UI
Michael Gillespie
added a comment - I can report that I've had less issues with this so far. I have disabled my work-around CORS extension, and haven't had problems with the sidebar disappearing for about a week now. 
Michael Gillespie
added a comment - I can report that I've had less issues with this so far. I have disabled my work-around CORS extension, and haven't had problems with the sidebar disappearing for about a week now. Michael Gillespie
added a comment - I am able to reproduce the issue mostly on the Browse Projects page, and the Browse Issues page. Sometimes the sidebar does not load at all, sometimes it loads as "placeholder" circles. I use the latest Chrome (Version 63.0.3239.132 (Official Build) (64-bit) as of now) on Windows 10 1709.
I cannot reproduce the issue in the latest Chrome Canary, Firefox, or IE, so it must be an issue with Chrome. The issue also does not occur in Incognito mode in Chrome.
Flushing the browser cache (Ctrl+F5) works as a temporary solution, but it comes back after a few navigations.
I have been able to get the sidebar working 100% by injecting CORS headers via an extension: https://chrome.google.com/webstore/detail/allow-control-allow-origi/nlfbmbojpeacfghkpbjhddihlkkiljbi/reviews?hl=en
The following error shows in the console when the sidebar disappears.
`Access to Script at 'https://jira-frontend.prod.atl-paas.net/assets/vendor.27d1802e884647e66da2.5.js' from origin 'https://[redacted].atlassian.net' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'https://[redacted].atlassian.net' is therefore not allowed access.`
In Firefox, I can confirm the correct header is sent from the server though, so I can only assume this CORS header is either not being served to Chrome, or is being blocked on the client end.
Michael Gillespie
added a comment - I am able to reproduce the issue mostly on the Browse Projects page, and the Browse Issues page. Sometimes the sidebar does not load at all, sometimes it loads as "placeholder" circles. I use the latest Chrome (Version 63.0.3239.132 (Official Build) (64-bit) as of now) on Windows 10 1709.
I cannot reproduce the issue in the latest Chrome Canary, Firefox, or IE, so it must be an issue with Chrome. The issue also does not occur in Incognito mode in Chrome.
Flushing the browser cache (Ctrl+F5) works as a temporary solution, but it comes back after a few navigations.
I have been able to get the sidebar working 100% by injecting CORS headers via an extension: https://chrome.google.com/webstore/detail/allow-control-allow-origi/nlfbmbojpeacfghkpbjhddihlkkiljbi/reviews?hl=en
The following error shows in the console when the sidebar disappears.
`Access to Script at 'https://jira-frontend.prod.atl-paas.net/assets/vendor.27d1802e884647e66da2.5.js' from origin 'https://[redacted].atlassian.net' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'https://[redacted].atlassian.net' is therefore not allowed access.`
In Firefox, I can confirm the correct header is sent from the server though, so I can only assume this CORS header is either not being served to Chrome, or is being blocked on the client end.
neerupama@rentrezi.com
added a comment - This ticket should be marked with highest priority as it is impacting business.
neerupama@rentrezi.com
added a comment - This ticket should be marked with highest priority as it is impacting business.
Me too. I have not observed this issue in a while.