Uploaded image for project: 'Jira Service Management Data Center'
  1. Jira Service Management Data Center
  2. JSDSERVER-6606

Blank/White screen when opening some Service Desk requests from the customer portal

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Highest Highest
    • 4.4.3, 3.16.11, 4.5.3
    • 4.4.0, 4.4.1, 4.4.2, 3.16.11, 3.16.8
    • Customer Portal
    • None

      Issue Summary

      If a Service Desk ticket contains mentions of other tickets in public comments, a customer won't be able to open this ticket if this user does not have access to the mentioned tickets, and will see a blank page.

      The issue can also occur when hyperlinks to other sites are mentioned in either the ticket summary or ticket description

      Steps to reproduce

      • Install Service Desk 4.4.2
      • Create a new Service Desk project
      • Create a customer account in this project (let's call the user customer1)
      • Create 2 tickets in the Service Desk project:
        • 1 ticket that customer1 has access to, by being the reporter or a participant (let's call this ticket BASICSD-2)
        • 1 ticket that customer1 does not have access to (let's call this ticket BASICSD-3)
      • Log into Jira as an agent
      • Open BASICSD-2, add a new public comment and include the internal URL of the issue BASICSD-3 (<JIRA_BASE_URL>/browse/BASICSD-3) in the comment
      • Log into the customer portal as the user customer1
      • Go to My Requests, and click on the request BASICSD-2

      Expected results

      The request BASICSD-2 should be opened in the customer portal.

      Actual results

      • The request BASICSD-2 can't be opened and the following happens:
        • the ticket shows as a blank screen and a 500 error is thrown in the UI
        • the following error is thrown in the Jira logs:
          2019-10-18 10:03:12,746 http-nio-8080-exec-10 ERROR xxxxxx XXXxXXXXxX ubczia XXX.XX.XX.XX /servicedesk/customer/portal/1/ABC-123 [o.a.c.c.C.[.[localhost]..[default]] Servlet.service() for servlet [default] threw exception
          java.lang.NullPointerException
                  at java.util.regex.Matcher.appendReplacement(Matcher.java:804)
                  at com.atlassian.servicedesk.internal.feature.customer.request.UrlReplacer.replace(UrlReplacer.java:41)
                  at com.atlassian.servicedesk.internal.feature.customer.request.IssueUrlConverterImpl.replaceIssueUrlsWithPortalRequestUrls(IssueUrlConverterImpl.java:71)
                  at com.atlassian.servicedesk.internal.feature.customer.request.CustomerTextRendererImpl.updateCustomerTextIntertal(CustomerTextRendererImpl.java:165)
                  at com.atlassian.servicedesk.internal.feature.customer.request.CustomerTextRendererImpl.updateTextForCustomer(CustomerTextRendererImpl.java:150)
                  at com.atlassian.servicedesk.internal.feature.customer.request.CustomerTextRendererImpl.renderComment(CustomerTextRendererImpl.java:84)
                  at com.atlassian.servicedesk.internal.feature.customer.request.activitystream.responses.ActivityResponseManagerImpl.buildCommentResponse(ActivityResponseManagerImpl.java:96)
                  at com.atlassian.servicedesk.internal.feature.customer.request.activitystream.responses.ActivityResponseManagerImpl.getResponse(ActivityResponseManagerImpl.java:72)
                  at 
          
      • In some situations, requests on the portal won't be shown at all:

      Workaround

      2 possible workarounds:

      1. Remove the URL <JIRA_BASE_URL>/browse/BASICSD-3) from the comment added to BASICSD-2
      2. Add the impacted user (customer1) as a participant of the request BASICSD-3

        1. CustomerPortal_View.png
          103 kB
          Julien Rey
        2. JIRA_UI.png
          442 kB
          Julien Rey
        3. screenshot-1.png
          30 kB
          Marko Filipan

          Form Name

            [JSDSERVER-6606] Blank/White screen when opening some Service Desk requests from the customer portal

            D.R. added a comment -

            @MercyShips RoleAccount:

            Atlassian is at SD version 4.12.0 now, perhaps consider upgrading your staging environment?

            This bug will remain when you stay on a lower version..

            D.R. added a comment - @MercyShips RoleAccount: Atlassian is at SD version 4.12.0 now, perhaps consider upgrading your staging environment? This bug will remain when you stay on a lower version..

            We are on service desk 4.5.4 and continue to have this issue on occasion. 

            MercyShips RoleAccount added a comment - We are on service desk 4.5.4 and continue to have this issue on occasion. 

            Hi, on 4.3.0 it is happening too

            Francisco Gomez Balastegui added a comment - Hi, on 4.3.0 it is happening too

            Julien Rey added a comment -

            dirk.ronsmans, thanks for the update, and please let us know if you still run into the bug after the upgrade

            Julien Rey added a comment - dirk.ronsmans , thanks for the update, and please let us know if you still run into the bug after the upgrade

            D.R. added a comment -

            Hello Julien,

            With the added info that it might still be an issue in 4.5.0 (and fixed in 4.5.3 and up) we will be upgrading as well.

            Should we encounter it again we'll ofcourse let you know! (but George his comment is already giving me hope)

            D.R. added a comment - Hello Julien, With the added info that it might still be an issue in 4.5.0 (and fixed in 4.5.3 and up) we will be upgrading as well. Should we encounter it again we'll ofcourse let you know! (but George his comment is already giving me hope )

            Julien Rey added a comment -

            george.dinkov,

            That's really good to hear! thanks for letting us know that you haven't hit this bug again after the last upgrade.

            Julien Rey added a comment - george.dinkov , That's really good to hear! thanks for letting us know that you haven't hit this bug again after the last upgrade.

            Hi Julien,

            Thank you for the update!

            We already upgraded a couple of weeks ago and so far we haven't hit this bug again. Will let you know if it comes up.

            Thanks,
            George

            George Dinkov (Botron) added a comment - Hi Julien, Thank you for the update! We already upgraded a couple of weeks ago and so far we haven't hit this bug again. Will let you know if it comes up. Thanks, George

            Julien Rey added a comment -

            dirk.ronsmans and george.dinkov, thanks for your comment regarding the versions that still have the bug.
            Can you try to upgrade Service Desk to 4.5.3 or any higher version and let us know if the bug is still reproducible?

            Best.

            Julien Rey added a comment - dirk.ronsmans and george.dinkov , thanks for your comment regarding the versions that still have the bug. Can you try to upgrade Service Desk to 4.5.3 or any higher version and let us know if the bug is still reproducible? Best.

            D.R. added a comment -

            Indeed, 4.5.0, still an issue!

            D.R. added a comment - Indeed, 4.5.0, still an issue!

            I can also confirm that this is still occurring with JSD 4.5.2. Please reopen the bug.

            Thanks!

            George Dinkov (Botron) added a comment - I can also confirm that this is still occurring with JSD 4.5.2. Please reopen the bug. Thanks!

              Unassigned Unassigned
              jrey Julien Rey
              Affected customers:
              3 This affects my team
              Watchers:
              23 Start watching this issue

                Created:
                Updated:
                Resolved: