Uploaded image for project: 'Jira Server and Data Center'
  1. Jira Server and Data Center
  2. JRASERVER-44981

Hiding Priority or Resolution Field Causes Issues To Not Be Displayed When Viewing A Project Board

    XMLWordPrintable

    Details

      Description

      NOTE: This bug report is for JIRA Server. Using JIRA Cloud? See the corresponding bug report.

      Summary

      Hiding Priority or Resolution, field causes the error message "The JIRA server could not be contacted. This may be a temporary glitch or the server may be down." to appear when viewing a Project > Issues.

      Environment

      JIRA v7.0.0-OD-02-247

      Steps to Reproduce

      1. Go to Field Configurations
      2. Hide Priority Field
      3. Go to a project using the field configuration
      4. See error message and no issues displayed

      Expected Results

      Issues should still display

      Actual Results

      No error is shown in the JIRA log.

      Error message that appears

      The JIRA server could not be contacted. This may be a temporary glitch or the server may be down.
      

      What console displays:

      /rest/issueNav/1/issueTable Failed to load resource: the server responded with a status of 400 (Bad Request)
      batch.js:216 DEPRECATED - Persistent: false has been deprecated and will be removed in a future release. 
           at showMsg (https://d1ixbz5qgnvms3.cloudfront.net/instance.atlassian.net/s/c5c95a3c91…_super/batch.js?atlassian.aui.raphael.disabled=true&locale=en-US:2531:1465)
      

      Workaround

      Go to Field Configuration and change Priority or Resolution to Show
      or
      Change the "Order by" option to a visible field

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              ohernandez@atlassian.com Oswaldo Hernandez (Inactive)
              Reporter:
              jaguilar Javier Aguilar (Inactive)
              Votes:
              7 Vote for this issue
              Watchers:
              23 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: