JIRA Service desk API - Malformed JSON being sent to API from customer portal

[glenberry]

We have a new installation of JIRA service desk that we are preparing for production.  In testing, we found that certain links did not work in Microsoft Edge. 

After doing some research with Fiddler/Postman I was able to determine that we were receiving a 500 error response from the API.  The POST request to the API from Service Desk did not have a value populated in the portalid, whereas the request from Chrome contained this: portalid=1.

I reproduced the issue with Postman.  Once I set the value of portalid to 1, I received a proper JSON response from the API.

Does JIRA Service Desk not support Edge?  Has anyone else encountered this issue and if so, do they know of a setting I can change or a workaround?  To be clear, the request is being sent from the out-of-the-box JIRA Service Desk application.

[Earl McCutcheon]

Hi Glen,

Edge is supported and we should not see any differences in the links response behavior between chrome and edge, so this defiantly sounds like a BUG.

Can you please provide some more details on the steps to reproduce and I will see if I can reproduce this locally, primarily:

• what links in the portal are you clicking that are not returning the proper portalid
• what version of Service Desk are you on
• What version of edge

Also just to rule out any other possible browser issue check out the tests in this KB article .

Regards,
Earl

[glenberry]

Hey Earl.  Thanks for getting back to me.  Answers to your questions:

1.  Links that would not redirect are:

/servicedesk/customer/user/requests?status=open

/servicedesk/customer/user/requests?status=open&reporter=all

/servicedesk/customer/portals

2. JIRAServiceDesk240618205828 - Atlassian JIRA 7.10.1

3. Edge 16

I'd be happy to provide more troubleshooting info.  Please let me know if you are able to repro. I will check out that KB article.  Thanks.

[Earl McCutcheon]

Hi Glen,

Thanks for the info and I was able to reproduce the error without issue and this is defiantly a new BUG, I filed the following request to track this:

• https://jira.atlassian.com/browse/JSDSERVER-5944

Playing around with the browser setting a bit I was not able to find a more graceful workaround other than simply refreshing the page which bypasses the error loading the correct page link, but its not a very intuitive for your customers accessing the site so please make sure to add yourself as a watcher to the request to get updates on the fix, or if we can find a better workaround in the mean time.

Regards,
Earl

[glenberry]

Thanks Earl.  I'm watching the issue.