This issue still seems to exist in 3.8.1 ?

Has the JIRA Service Desk for Cloud received this fix? We're seeing a similar issue with JSD Cloud.

Hi,

What is the fastest way to upgrade JSD from 3.3.2 to 3.5?
Can you provide some hints.

All the best,
Miroslav

Released as part of JSD 3.4.0 https://confluence.atlassian.com/servicedesk/jira-service-desk-3-4-x-release-notes-874627018.html#JIRAServiceDesk3.4.xReleaseNotes-3-4-0

• JIRA Service Desk Team

Upgraded to JSD 3.4.0 and performed testing on Windows 10 and IE11.

Can now see the login page.

Can now login and view support issues.

Problem appears to be fixed in our JSD environment.

Updated my test server to Software 7.3.3 and SD 3.4.0 and this did not resolve my problems. I will open a separate ticket to troubleshoot further.

Downloaded and applied 3.4 this morning, all works as expected.  Thanks.

The workaround described may work, but seems really "hacky" and will not be possible to perform for most customers. 

Hotfix version needs to be released asap, and the version 3.3.2 should be withdrawn as this is a blocking bug for many customers. 

We tried Vladimir's way but that didn't work. Does Atlassian already have a ETA for release 4.3.0? 

Daniel and Vladimir,

I had success using Vlad's fix to get IE 11 working in our environment as well. I commented on the answer page if anyone wants to see the process I used. We are running our JIRA environment on Windows Server 2008 R2.

incredible...

This is frankly ridiculous.   Why is this not being hot fixed and why is the release not pulled with this known major bug (I downloaded and installed just this morning)?   We as end users cannot be expected to deploy another browser just because proper testing wasn't done with this service desk release.   I believe everyone on this ticket pays for support and this work around is not acceptable.

Daniel, we have fixed this issue with success after we have replaced the arrow functions. The customer portal could not work in your case because of some third party plugins which runs scripts on the portal and has issues with IE or it could be just cache issue.

FYI, I tried Vlad's fix that Toby referred to replacing the arrow functions with normal functions and the customer portal is still not working for me in IE. I'm not sure if anyone else has had success with this fix.

Please fix as soon as possible. Downgrade is not an option.

Is there an expected release timeframe for JSD 3.4.0?

3.4.0 is the next scheduled JSD release, that will remain compatible with JIRA 7.3.x

Why is this fix being held until 3.4.0? Surely an issue causing issues with a supported configuration should be pushed to a hot fix release.

The issue has seemingly been pinned down here: https://answers.atlassian.com/questions/60968041/jira-servicedesk-3.3.2-customer-portal-not-working.-how-to-fix-it so this should not be a complicated change.

Same here, we updated customers' JSD to 3.3.2 and ran into above mentioned bug. Unfortunately, we pushed our client to update their system and can't move backwards. 

We are facing the same problem. It would be great if you could fix this very soon.

Thanks!

I see 3.3.2 is still available to download, it might be a good idea for Atlassian to pull that version to limit the impact.

Disappointed to see this still 'untriaged, low priority' after 3 days.  We need to decide on an action plan to rollback to a stable revision (3.3?) by EOD today.  I was hoping to see some movement here beforehand.   Our preference would be to move forward instead of backwards.

This issue is affecting our issue reporters who use IE and we were advised to rollback to the older version too. But, it has been three days since we rolled out the latest version and I have around 450 tickets already. Suggestion from Service Desk Support team is to send them the xml backup and list of plugins we have, so that they can confirm if it is possible to rollback without losing the data. This surprised me a little. List of plugins, I can share that... not the back up. but Why do you need the it?! that would include all our customer data. We are trying to find a workaround ourselves while redirecting lot of users to other browsers.

I would really appreciate if you pick this up and provide a standard fix faster. Thanks!

I hit this today and was advised to rollback to 3.3.1 which I did in test but I saw the same behavior in the portal where it would not render the portal at all.  In 3.3.1 the queues did become visible again.  3.3.1 seems to be fine as well, the redirect for my portal in our test environment was incorrect.

This issue affects our live customers since we upgraded to last SD version today.

We can not move to another browser since our main partner is Microsoft who works on IE 11.

I will appreciate increasing the priority of the issue and preparing a fix in a nearest time.

Thank you!