Issue Page Shows Up Blank After Upgrade

Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.

Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible

Summary

Problem

After upgrading to Jira 8.12.0 or higher, when trying to view issues, the page is shown blank except for the navigation bar at the top of the page.

The screen may look similar to this:

(Auto-migrated image: description temporarily unavailable)

Log Errors

The following error is seen in the atlassian-jira.log file.

2021-01-08 15:36:18,235-0600 http-nio-48120-exec-11 ERROR shall 936x250x1 7ah4j8 0:0:0:0:0:0:0:1 /issues/ [c.atlassian.velocity.DefaultVelocityManager] MethodInvocationException occurred getting message body from Velocity: java.lang.NullPointerException java.lang.NullPointerException at sun.misc.FloatingDecimal.readJavaFormatString(FloatingDecimal.java:1838) at sun.misc.FloatingDecimal.parseDouble(FloatingDecimal.java:110) at java.lang.Double.parseDouble(Double.java:538) at java.lang.Double.valueOf(Double.java:502) at com.atlassian.jira.plugin.issuenav.properties.ParsingApplicationProperties.getFromProperty(ParsingApplicationProperties.java:49) at com.atlassian.jira.plugin.issuenav.properties.ParsingApplicationProperties.getDouble(ParsingApplicationProperties.java:30) at com.atlassian.jira.plugin.issuenav.IssueNavAction.getJqlAutocompleteQueryDelay(IssueNavAction.java:838) ... 3 filtered

Diagnosis

Environment

  • When upgrading to a Jira Server or Data Center version 8.12.0 and above.

  • When copying a jpm.xml file from a previous version or modifying it.

Diagnostic Steps

  • Go to atlassian-jira.log and search for a recent restart of Jira to view the list of modified files being used by the instance.

    ___ Modifications ___________________________ Modified Files : jpm.xml

Cause

The issue is caused by missing properties that were added to the jpm.xml staring in Jira 8.12.0. The changes were made as a response to resolve the following feature suggestion.

JRASERVER-71248 Provide a way to configure the frequency at which JQL autocomplete suggestions may submit search requests.

The following properties were added to the jpm.xml starting in Jira 8.12.0.

<property> <key>jira.jql.autocomplete.query.delay</key> <description>Delay in seconds that determines how much to wait for new keystrokes in JQL autocomplete before sending search request. This determines the frequency at which JQL autocomplete suggestions may submit requests. This setting is used only when JQL Auto-complete is enabled in System >> General Configuration.</description> <default-value>0.3</default-value> <!-- Related to JRASERVER-71248, JSWSERVER-20272 --> <type>double</type> <admin-editable>false</admin-editable> <sysadmin-editable>false</sysadmin-editable> <requires-restart>true</requires-restart> </property> <property> <key>jira.jql.autocomplete.min.query.length</key> <description>Min number of characters to be typed in JQL autocomplete query before suggestion search request is made. 0 means we start suggesting as soon as we type. This setting is used only when JQL Auto-complete is enabled in System >> General Configuration.</description> <default-value>0</default-value> <!-- Related to JRASERVER-71248, JSWSERVER-20272 --> <type>uint</type> <admin-editable>false</admin-editable> <sysadmin-editable>false</sysadmin-editable> <requires-restart>true</requires-restart> </property>

ℹ️ Note: Although some application vendors may request changes to the jpm.xml file, these changes can potentially break Jira. Instead of editing jpm.xml directly, our recommendation is to make any configuration changes in your jira-config.properties file, as noted here: Advanced Jira application configuration

Solution

Use the jpm.xml file made for the version of Jira you are running. Don't modify or copy a jpm.xml file from a previous version.

Resolution Steps

  • If you don't have a backup of the default jpm.xml, download Jira using the ZIP Archive option here:

  • After unzipping the archive, the jpm.xml file can be found in the following path:

    • atlassian-jira-software-8.x.x-standalone/atlassian-jira/WEB-INF/classes/jpm.xml

  • Update your current Jira instance with the jpm.xml file from the previous step

  • Restart Jira

Updated on April 2, 2025
Platform
Data Center only
Product
Jira Software Data Center
On this pageSummaryDiagnosisCauseSolution

Still need help?

The Atlassian Community is here for you.
Ask the Community