Problem

      On a JIRA Service Desk instance with JIRA Software once removed from the same instance, clicking on the link to view the error details and repair the problem doesn't work.

      Environment/Prerequisite

      A JIRA Service Desk instance with JIRA Software removed from the same instance

      Steps to reproduce the issue

      1. Create a new Service Desk project or go to any existing Service Desk project.
      2. Go to Project settings.
      3. Go to Screen.
      4. Remove Summary field from the screen.
      5. Go back to the Service Desk project's Queues page.
      6. An error will appear on the top right side of the page with a link to View error details and repair the problem.
      7. Click on the link.

      Expected result

      A dialog box with the details of the error will appear.

      Actual result

      The link is clickable but no response.

      Workaround

      • Use the URL below to view the error. Make sure to replace {Project_Key_Goes_Here} with the Key of the impacted project
        <JIRA_base_URL>/rest/servicedesk/1/servicedesk/{Project_Key_Goes_Here}/precondition
        
      • Reinstall JIRA Software application into the instance would fix this too.

        1. configurationError.png
          configurationError.png
          35 kB
        2. dialog box.png
          dialog box.png
          734 kB
        3. error message.png
          error message.png
          711 kB

          Form Name

            [JSDSERVER-5173] "View error details and repair the problem" link not working

            This issue is resolved in latest version (4.9.0)


            Nafis Faramarzi added a comment - This issue is resolved in latest version (4.9.0)

            Thank you so much I appreciated

            aashish gupta added a comment - Thank you so much I appreciated

            I have the same problem, but when I use the link above I see the results as "{"alerts":[]}" 

            I replaced the "<JIRA_base_URL>" with my instance URL

            I replaced the "{Project_Key_Goes_Here}" with the project key 

            Do I need to change the number "1" ? 

            Any help is appreciated. 

            Narasimha Tunuguntla added a comment - I have the same problem, but when I use the link above I see the results as "{"alerts":[]}"  I replaced the "<JIRA_base_URL>" with my instance URL I replaced the "{Project_Key_Goes_Here}" with the project key  Do I need to change the number "1" ?  Any help is appreciated. 

            Precondition URL worked. Thanks for sharing!

            Hari Vaddepally added a comment - Precondition URL worked. Thanks for sharing!

            Having the same issue, when click on the issue, nothing happens, when used the workaround, I got the error. Please fix this

             

            Jaime Forero added a comment - Having the same issue, when click on the issue, nothing happens, when used the workaround, I got the error. Please fix this  

            Sami added a comment -

            Even I had the same problem after installing Jira 7.11 & JSD 3.14 but thank god workaround "Prediction" URL help us. 

             

            @Michell Chin thanks for the workaround solution. 

            Sami added a comment - Even I had the same problem after installing Jira 7.11 & JSD 3.14 but thank god workaround "Prediction" URL help us.    @Michell Chin thanks for the workaround solution. 

            I had the same problem with JIRA Software installed. 

            JIRA Software 7.5.0

            JIRA Service Desk 3.8.1

            The workaround with 'precondition' URL helped.

            Andre Kolodochka added a comment - I had the same problem with JIRA Software installed.  JIRA Software 7.5.0 JIRA Service Desk 3.8.1 The workaround with 'precondition' URL helped.

              14858f4147da Nafis Faramarzi
              michin Michelle Chin
              Affected customers:
              30 This affects my team
              Watchers:
              34 Start watching this issue

                Created:
                Updated:
                Resolved: