I get the following Exception when I attempt to view the status list
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.
I already followed the steps to check for orphaned Workflows and Schemes and the queries didn't find anything.
I would appreciate any help
-Sara
Hi Sara,
In order to diagnose this further can I have the output of the commands from:
select * from nodeassociation where SOURCE_NODE_ENTITY='Project' AND SOURCE_NODE_ID not in (select ID from project);
select * from nodeassociation where SOURCE_NODE_ENTITY='Project' AND SOURCE_NODE_ID not in (select ID from project);
SELECT count(*), parentname FROM jiradraftworkflows group by parentname having count(*) > 1;
SELECT count(*), workflowname FROM jiraworkflows group by workflowname having count(*) > 1;
In addition, do you see anything in your logs near these lines similar to the following:
Caused by: com.atlassian.cache.CacheException: java.lang.IllegalStateException: There are more than one draft workflows associated with the workflow named '<workflow name>'
Let me know.
Cheers,
Branden
Brenden -
Thanks for the response. I get empty result sets for all of those queries, and there is no Cache Exception.
Thanks
-Sara
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Sara,
Thanks for the update. Please try one more thing and we'll go from there. Please go to the database integrity checker and run it. If it finds any errors choose the option to fix them:
After the selected checks run, the preview screen will be shown.
The screen provides details about the existing data inconsistencies. If any inconsistencies were found, the 'Fix' button will also appear on the page. The messages in red describe inconsistencies that the check will correct if it is chosen and the 'Fix' button is clicked. Messages that appear in yellow are warnings that the check will not correct; JIRA will auto-recover from these inconsistencies when an action is taken on an issue.
Select any inconsistencies that you would like to correct, then click the 'Fix' button.
Cheers,
Branden
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Branden -
I ran the database integrity checker and it found an item, which I then used the 'FIX' button to correct (see screenshot)
I am still getting the 500 error :-(
I re-ran the integrity checker and it didn't find anything the second time. I also re-ran the queries and still no results.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Sara,
Thank you for trying those steps. I've created a ticket with our Support team and someone should be reaching out to you shortly. Once you do get the issue resolved please let the Community know what the fix was in case someone else runs into this issue.
Cheers,
Branden
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.