Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.

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

Problem

When creating a new project, you will see an error on the Priority Scheme when you navigate to Project > Project Settings. 

Error rendering 'com.atlassian.jira.jira-project-config-plugin:summary-priorities'. Please contact your JIRA administrators.

The following appears in the atlassian-jira.log

2018-01-28 08:44:01,644 http-nio-8080-exec-83 ERROR admin 524x16588x1 1jj4krp 84.196.64.99,172.19.0.2 /plugins/servlet/project-config/TEST/summary [c.a.j.web.component.ModuleWebComponentImpl] An exception occured while rendering the web panel: com.atlassian.jira.jira-project-config-plugin:summary-priorities (null)
com.google.template.soy.tofu.SoyTofuException: In 'print' tag, expression "$priorityScheme.name" evaluates to undefined.
	at JIRA.Templates.ProjectSummary.priorities(summary-priorities.soy:15)
	at com.google.template.soy.tofu.internal.BaseTofu.renderMainHelper(BaseTofu.java:369)
	at com.google.template.soy.tofu.internal.BaseTofu.renderMain(BaseTofu.java:322)
	at com.google.template.soy.tofu.internal.BaseTofu.access$100(BaseTofu.java:66)
	at com.google.template.soy.tofu.internal.BaseTofu$RendererImpl.render(BaseTofu.java:476)
	at com.atlassian.soy.impl.DefaultSoyManager.render(DefaultSoyManager.java:133)
	at com.atlassian.soy.impl.DefaultSoyTemplateRenderer.render(DefaultSoyTemplateRenderer.java:45)
...
Caused by: com.google.template.soy.sharedpasses.render.RenderException: In 'print' tag, expression "$priorityScheme.name" evaluates to undefined.
	at JIRA.Templates.ProjectSummary.priorities(summary-priorities.soy:15)
	at com.google.template.soy.sharedpasses.render.RenderVisitor.visitPrintNode(RenderVisitor.java:250)
	at com.google.template.soy.soytree.AbstractSoyNodeVisitor.visit(AbstractSoyNodeVisitor.java:87)
	at com.google.template.soy.soytree.AbstractSoyNodeVisitor.visit(AbstractSoyNodeVisitor.java:56)
	at com.google.template.soy.basetree.AbstractNodeVisitor.visitChildren(AbstractNodeVisitor.java:59)
	at com.google.template.soy.sharedpasses.render.RenderVisitor.visitBlockHelper(RenderVisitor.java:702)
...

Diagnosis

Environment

• The instance may have been migrated from Cloud environment and merged some data from JIRA server, among other possible causes.

• Run the below SQL query to determine the ID of the Default Priority Scheme.

  select * from fieldconfigscheme where configname = 'Default priority scheme';

• The next SQL query will tell us whether the Default Priority Scheme has an entry on the configurationcontext table.

  select * from configurationcontext where customfield = 'priority' and project is null and fieldconfigscheme = <ID of the Default Priority Scheme>;

   The null value for the project column indicates that this is a global default configuration for projects.

Cause

There is no row for the default priority scheme in configurationcontext table.  

 There must be at least one row in configurationcontext table that is not mapped to any project. This row is used to tell Jira which priority scheme is the default.

Workaround

The error can be resolved by navigating to Administration > Issues > Priority Scheme and associate the new project to any of the existing Priority Scheme.

Resolution

1.  Backup the JIRA database so that there's a fallback in case something goes wrong.

2.  Run the following SQL insert query:

    insert into configurationcontext values ((select max(id)+1 from configurationcontext), NULL, NULL, 'priority', <ID of the Default Priority Scheme>);

3. Restart JIRA.