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

"View error details and repair the problem" link not working

    XMLWordPrintable

Details

    Description

      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.

      Attachments

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

        Issue Links

          Activity

            People

              14858f4147da Nafis Faramarzi
              michin Michelle Chin
              Votes:
              30 Vote for this issue
              Watchers:
              34 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Backbone Issue Sync