Issue Navigator displays an error when searching for certain issues

Still need help?

The Atlassian Community is here for you.

Ask the community


When you search the Issue Navigator, you get the message "An error occurred whilst rendering this message. Please contact the administrators, and inform them of this bug."

The following appears in the atlassian-jira.log:

2013-08-03 16:04:13,960 http-apr-8080-exec-5 ERROR admin 964x14x1 xxxxx /issues/ [velocity] Exception in macro #issues at templates/jira/issue/table/issuetable-issue.vm[line 3, column 1]
2013-08-03 16:04:13,961 http-apr-8080-exec-5 ERROR admin 964x14x1 xxxxx /issues/ [com.atlassian.velocity.DefaultVelocityManager] MethodInvocationException occurred getting message body from Velocity: java.lang.NullPointerException
	at com.atlassian.jira.permission.PermissionContextImpl.getRelevantStepDescriptor(
	at com.atlassian.jira.permission.WorkflowPermissionFactory.getWorkflowPermissions(
	at  <+3>
	at java.lang.reflect.Method.invoke(Unknown Source)
	at com.atlassian.util.profiling.object.ObjectProfiler.profiledInvoke(
	at com.atlassian.jira.config.component.SwitchingInvocationHandler.invoke(
	at $Proxy80.hasPermission(Unknown Source)
	at com.atlassian.velocity.DefaultVelocityManager.getEncodedBody(
	at com.atlassian.jira.template.velocity.DefaultVelocityTemplatingEngine$DefaultRenderRequest.asHtml(
	at com.atlassian.jira.web.component.AbstractWebComponent.getHtml(
	at com.atlassian.jira.web.component.IssueTableWebComponent$1.write(
	at com.atlassian.jira.web.component.IssueTableWebComponent.getHtml(
	at com.atlassian.jira.web.component.IssueTableWebComponent.getHtml(
	at com.atlassian.jira.bc.issue.table.DefaultIssueTableService.createIssueTable(
	at com.atlassian.jira.bc.issue.table.DefaultIssueTableService.getIssueTable(
	at com.atlassian.jira.bc.issue.table.DefaultIssueTableService.getIssueTableFromFilterWithJql(  <+3>
	at java.lang.reflect.Method.invoke(Unknown Source)
	at com.atlassian.multitenant.impl.MultiTenantComponentFactoryImpl$AbstractMultiTenantAwareInvocationHandler.invokeInternal(
	at com.atlassian.multitenant.impl.MultiTenantComponentFactoryImpl$MultiTenantAwareInvocationHandler.invoke(
	at $Proxy395.getIssueTableFromFilterWithJql(Unknown Source)  <+3>


There's a workflow scheme which is associated to a non-existent workflow.



In order to confirm that please execute the following SQL query (made in PostgreSQL)

select * from workflowschemeentity where workflow not in (select workflowname from jiraworkflows)


Always back up your data before performing any modification to the database. If possible, try your modifications on a test server.


The workflow scheme should be updated manually with a valid workflow first via UI (if possible) else, it has to be modified in the database, as well as any entries associated to the invalid workflow at the changeitem and os_wfentry tables. The steps to perform this are as follows:

  • Shutdown JIRA
  • Run the update statements to change the non-existent workflow name to the valid workflow
  • Restart JIRA
  • Use the following update statements as an example of how it should look

    UPDATE workflowschemeentity
    SET workflow = 'valid workflow'
    WHERE workflow = 'non-existent workflow';
    UPDATE changeitem
    SET newstring = 'valid workflow'
    WHERE newstring = 'non-existent workflow';
    UPDATE os_wfentry
    SET name = 'valid workflow'
    WHERE name = 'non-existent workflow';

Last modified on Jan 20, 2017

Was this helpful?

Provide feedback about this article
Powered by Confluence and Scroll Viewport.