Receiving a 500 error when viewing Issue Statuses

joe_dinunzio

When accessing System > Issues > Statuses: all users are receiving a 500 error:

 

 

 

We are on a very old instance 6.3.4 but it has been stable until recently. I am at a loss what to check next, the only other 500 error support items I can find relate to different areas within JIRA such as workflows. Here are more details from the error:

 

Referer URL: https://---------------/secure/admin/ViewIssueTypes.jspa

com.google.template.soy.tofu.SoyTofuException: In template JIRA.Templates.Statuses.success: In 'foreach' command {foreach $status in $statuses}{call .statusRow}{param status: $status /}{/call}{/foreach}, the data reference does not resolve to a SoyListData.

 

 

Andy Heinzer

Hi Joe,

This specific error is thrown when your Jira database has a duplicate draft workflow and/or when there are orphaned scheme references such as permissions, notifications etc.   There is a comprehensive KB on this specific error in The JIRA application statuses page throws a 500 Error.

There are a pair of diagnosis queries you can run on the SQL database of Jira to determine if what steps would be taken next:

Run the following SQL query on the database (to identify the drafts with more than one entry):

SELECT count(*), parentname FROM jiradraftworkflows group by parentname having count(*) > 1;

For the workflows(not draft), run the following query :

SELECT count(*), workflowname FROM jiraworkflows group by workflowname having count(*) > 1;

 

and also:

DIAGNOSIS: ORPHANED ROWS IN THE NODEASSOCIATION TABLE

<span>select</span> <span>*</span> <span>from</span> nodeassociation <span>where</span> SOURCE_NODE_ENTITY<span>=</span><span>'Project'</span> <span>AND</span> SOURCE_NODE_ID <span>not</span> <span>in</span> <span>(</span><span>select</span> ID <span>from</span> project<span>)</span><span>;</span>

 

Depending on which of these SQL queries return results will determine the next steps to take to resolve this.  If you have any questions or concerns about following that KB, please let me know the results to each of those SQL queries and I will try to help out.

Andy