How can query without an error when the query includes deleted issue?

[Kyoungsoon Kim]

I got the error messages below;

An error occurred whilst rendering this message. Please contact the administrators, and inform them of this bug. Details: ------- org.apache.velocity.exception.MethodInvocationException: Invocation of method 'getHtml' in class com.atlassian.jira.issue.fields.layout.column.ColumnLayoutItemImpl threw exception java.lang.NullPointerException: while trying to invoke the method com.atlassian.jira.issue.Issue.getKey() of a null object loaded from local variable 'parentIssue' at templates/jira/issue/table/macros.vm[line 117, column 34] at org.apache.velocity.runtime.parser.node.ASTMethod.handleInvocationException(ASTMethod.java:337) at org.apache.velocity.runtime.parser.node.ASTMethod.execute(ASTMethod.java:284) at org.apache.velocity.runtime.parser.node.ASTReference.execute(ASTReference.java:262) at org.apache.velocity.runtime.parser.node.ASTReference.value(ASTReference.java:507) at org.apache.velocity.runtime.parser.node.ASTExpression.value(ASTExpression.java:71) at org.apache.velocity.runtime.parser.node.ASTSetDirective.render(ASTSetDirective.java:142) at org.apache.velocity.runtime.parser.node.ASTBlock.render(ASTBlock.java:72) at org.apache.velocity.runtime.directive.Foreach.performIteration(Foreach.java:393) at org.apache.velocity.runtime.directive.Foreach.render(Foreach.java:316) at org.apache.velocity.runtime.parser.node.ASTDirective.render(ASTDirective.java:175) at org.apache.velocity.runtime.parser.node.ASTBlock.render(ASTBlock.java:72) at org.apache.velocity.runtime.directive.VelocimacroProxy.render(VelocimacroProxy.java:212) at org.apache.velocity.runtime.directive.RuntimeMacro.render(RuntimeMacro.java:247) at org.apache.velocity.runtime.parser.node.ASTDirective.render(ASTDirective.java:175) at org.apache.velocity.runtime.parser.node.ASTBlock.render(ASTBlock.java:72) at org.apache.velocity.runtime.parser.node.ASTIfStatement.render(ASTIfStatement.java:87) at org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:336) at org.apache.velocity.Template.merge(Template.java:328) at org.apache.velocity.Template.merge(Template.java:235) at org.apache.velocity.app.VelocityEngine.mergeTemplate(VelocityEngine.java:381) at com.atlassian.velocity.DefaultVelocityManager.writeEncodedBodyImpl(DefaultVelocityManager.java:117) at com.atlassian.velocity.DefaultVelocityManager.writeEncodedBody(DefaultVelocityManager.java:97) at com.atlassian.jira.template.velocity.DefaultVelocityTemplatingEngine$DefaultRenderRequest.toWriterImpl(DefaultVelocityTemplatingEngine.java:122) at

[Nic Brough -Adaptavist- · Accepted solution]

A query cannot include a deleted issue.  There's nothing there to include, a deleted issue is completely gone from the database.

I can see why you phrased the question like that, the error message says the parent issue for something is null, which implies it is deleted.  It may well be the right guess, in that it is deleted.

But the only way to get into a state where a child issue exists without a visible parent is to write code that breaks it (by ignoring data integrity, or messing up security) or messing with the database.  The only other way to get this message is if there is a broken index.

So, you have broken data somewhere, not a "need to include a deleted issue".  I would

• Log in as an admin
• Run the integrity checker - every option (although you may want to do one step at a time to avoid timing out)
• Do a full re-index at a time when the users won't need Jira

If it still happens, you'll need to read more of the log to find out what parent issue is missing and why

[Kyoungsoon Kim]

Thanks Nic for your kind explanation.

By the way, it works now after doing a Ctrl + F5 on the browser window.

Thanks again,