Navigation pane greyed out and no preview view Edited

We are running Jira from our own servers and have just upgraded to 7.5.0 since the upgrade I am having issues with the Boards View.

 

The Left hand side navigation buttons are all greyed out and pulsing also when I click on a ticket in the backlog it does not show me the summary in the right hand pain anymore?

 

Other users are not having this issue, just me and it seem to be a PC or browser related issue as I can log in via my mobile device and it all displays correctlyScreenHunter 205.png 

 

1 answer

Hi,

I believe that you are encountering a documented bug in Jira 7.2.x and higher versions.  This bug is currently being tracked in https://jira.atlassian.com/browse/JRASERVER-64095

At the moment, our development team is still trying to gather a more comprehensive view of the different possible causes for this kind of display error.   There is a recent note there that the 7.5.1 version of Jira is expected to be able to help gather more data on this problem.

 

In the meantime, there is a documented work-around on that page you can follow that might help prevent this display problem:

Workaround

Disable BigPipe. That will revert to pre 7.2 page rendering behaviour:

  • View Issue is going to take longer to load as big-piped panels (e.g.: Comments section, Projects Sidebar) will be rendered eagerly rather than postponed.

Steps:

  1. Navigate to http:<JIRA-base-URL>/secure/admin/SiteDarkFeatures!Default.jspa  to get to the Dark Features page.
  2. Enable the dark feature com.atlassian.jira.config.BIG_PIPE_KILLSWITCH

Please let me know if this helps.

Regards,
Andy

Thanks Andy 

I applied the fix as suggested. Ill this did was make the greyed out icons disappear it did not load anything after that.

 

I have determined that this is an issue on the PC as I have tried many other browsers but still get the same issue. I am wondering if it is a firewall and anti virus blocking issue . 

Sorry to hear this did not resolve this problem.  In this case, it would probably be best to undo this dark feature.  You can do this by returning to this page and clicking the disable button for this feature name.

Could you let me know a bit more about your environment and this recent upgrade?  Such as, what version of Jira were you running directly before going to 7.5.0?   And is your Jira instance operating behind a reverse proxy?

If you have a reverse proxy, or you aren't sure, it might help to try to follow the steps in How to bypass a Proxy and SSL to test network connectivity.   I am interested to see if you can connect directly to the Jira instance, without having the traffic redirect through a proxy to see if this makes any difference in the way the page is rendered.

Hi Andrew,
thanks for your reply. I did manage to fix this last night.
In Chrome under Settings, then under the advanced drop down tab I click on Reset and totally reset by browser.
On logging back into Jira that side bar now loading. This has fixed Chrome. I have not gotten around to IE yet

Thanks

Hi I managed to find the cause for this but not really sure why it affects the side bar 

If I enter out site using the HTTPS prefix the side tool bar does not load 

https://jira.uat.onegov....

 

However if I drop the HTTPS it loads correctly 

jira.uat.onegov.....

Interesting, it sounds like there might be a problem either with a reverse proxy in your environment or with the configuration of Jira to use that proxy.   I would be interested to check on your $JIRAINSTALL/conf/server.xml file.   This is the configuration file that determines how Jira hosts its own internal webserver (Tomcat).

It's possible to have tomcat using multiple connectors and SSL, but lots of environments instead choose to terminate SSL on a reverse proxy instead.  Jira can work in either setup, but if the connector in Jira is unaware there is a proxy, it can tend to cause weird page display issues like this.   For example if tomcat does not have a connector opening port 443 directly, then you likely need to make sure the connector being used by the proxy includes the parameters such as:

proxyName="jira.example.com"
proxyPort="443"
scheme="https"

These parameters are explained in Proxying Atlassian applications.

If you want to access Jira over both HTTP and HTTPS, I would recommend creating separate connectors in Tomcat to do this that operate on different port numbers.   This way can be helpful for testing this kind of problem.

But the fact that you found this works over http and not https is an indication that there is probably a problem with how HTTPS is configured in your environment.

This issue has come up on our instance.  When going to the link you provided to change settings, I am told I do not have permission, even though I am the site admin...

 

Please provide the next steps you would recommend. 

Hi @Peter Hagerty

Could you please clarify which link you are trying to follow steps on?   I am afraid I have listed a number of different links and addresses in the process of trying to help troubleshoot this problem in JNG's case.

Could you also let us know

  1. what version of Jira you are running now? 
  2. Did this problem just start after an upgrade?  If so, please let us know what version you upgraded from?
  3. Is this happening all the time? some of the time? or only on specific projects?

Thanks,

Andy

I had a problem following these steps:

  1. Navigate to http:<JIRA-base-URL>/secure/admin/SiteDarkFeatures!Default.jspato get to the Dark Features page.
  2. Enable the dark feature com.atlassian.jira.config.BIG_PIPE_KILLSWITCH

We are using v1001.0.0-SNAPSHOT#100079-sha1:75b11a8

I believe this issue occured when a user was using the new look and feel of Jira.  I don't have this type of issue when using the old look and feel.

The problem was resolved when resetting chrome following these steps: In Chrome under Settings, then under the advanced drop down tab I click on Reset and totally reset by browser.

Hi Peter,

Thanks for letting us know the resolution here for your instance.

In reviewing my first reply, I found a missing space that could have affected the URL.

However the other problem with you being unable to reach that page here is that the steps I posted are actually for Jira Server.  You cannot reach the dark features page of a Cloud instance.

Regards,

Andy

Suggest an answer

Log in or Sign up to answer
How to earn badges on the Atlassian Community

How to earn badges on the Atlassian Community

Badges are a great way to show off community activity, whether you’re a newbie or a Champion.

Learn more
Community showcase
Published yesterday in Jira Service Desk

Wy are we still using email for Service Desk workflows?

...attest to the experience of an urgent approval that gets lost in the boss’s inbox and requires that special “Please Approve” email or text message. In an age where we have distributed teams...

54 views 0 2
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you