500 Error Page when Viewing Statuses

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

Symptoms

Going to JIRA Administration -> Issues -> Statuses results in a 500 Error Page with this message:

1 2 3 4 5 6 com.google.template.soy.tofu.SoyTofuException: In template JIRA.Template.Util.Issue.Status.statusLozenge: In 'print' tag, expression "$name" evaluates to undefined. at com.google.template.soy.tofu.internal.BaseTofu.renderMainHelper(BaseTofu.java:341) at com.google.template.soy.tofu.internal.BaseTofu.renderMain(BaseTofu.java:300) at com.google.template.soy.tofu.internal.BaseTofu.access$100(BaseTofu.java:56) at com.google.template.soy.tofu.internal.BaseTofu$RendererImpl.render(BaseTofu.java:427) ...

Diagnosis

  • Viewing an issue, the Status is rendered as Icon + Status Name instead of JIRA 6.2 Release Notes:

    (Auto-migrated image: description temporarily unavailable)
  • Editing a workflow, it's unable to add a new Status

    (Auto-migrated image: description temporarily unavailable)

Cause

Issue Status Lozenge is Disabled in a JIRA System File

Solution

Resolution

  • Shut down JIRA

  • Open JIRA_Install/atlassian-jira/WEB-INF/classes/jira-features.properties

  • Locate the line jira.issue.status.lozenge=false

  • Set it to jira.issue.status.lozenge=true

    ⚠️ If there's no such line, simply add it (jira.issue.status.lozenge=true)

  • Restart JIRA

Updated on April 2, 2025

Still need help?

The Atlassian Community is here for you.