Symptoms

This knowledge base article addresses the 2 issues below:

• Issue 1: After an upgrade, or migrating from Jira Cloud to Jira server, errors like the following appear in the atlassian-jira.log file:

  2008-06-09 14:39:51,150 http-8080-Processor10 ERROR [com.opensymphony.workflow.AbstractWorkflow] Error checking available actions
  com.opensymphony.workflow.WorkflowException: Could not load condition
  at com.opensymphony.workflow.AbstractWorkflow.passesCondition(AbstractWorkflow.java:900)
  at com.opensymphony.workflow.AbstractWorkflow.passesConditions(AbstractWorkflow.java:938)
  at com.opensymphony.workflow.AbstractWorkflow.passesConditions(AbstractWorkflow.java:936)
  at com.opensymphony.workflow.AbstractWorkflow.passesConditions(AbstractWorkflow.java:936)
  at com.opensymphony.workflow.AbstractWorkflow.passesConditions(AbstractWorkflow.java:962)
  at com.opensymphony.workflow.AbstractWorkflow.getAvailableActionsForStep(AbstractWorkflow.java:688)
  at com.opensymphony.workflow.AbstractWorkflow.getAvailableActions(AbstractWorkflow.java:118)
  at com.atlassian.jira.issue.IssueUtilsBean.loadAvailableActions(IssueUtilsBean.java:60)
  at com.atlassian.jira.web.component.issuesummary.IssueSummaryWebComponent.getAvailableActions(IssueSummaryWebComponent.java:90)
  at com.atlassian.jira.web.component.issuesummary.IssueSummaryWebComponent.getHtml(IssueSummaryWebComponent.java:68)
  at org.apache.jsp.decorators.issuesummary_jsp._jspService(issuesummary_jsp.java:369)
  at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97)
  at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
  at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:334)
  

• Issue 2: Migrating from Jira Cloud to Jira server, on the destination Jira Server, there are missing Workflow's Condition/Validator/Post-Functions. For example, users cannot transition ticket status, there're no buttons for transitioning for any ticket at any status using some of their workflows, which looks exactly the same as the one from cloud. The following appears in the atlassian-jira.log file:

  2020-04-13 17:34:57,659-0700 http-nio-8080-exec-3 ERROR guomin 1054x735x1 1tv7l9s 10.4.104.85 /secure/AjaxIssueAction!default.jspa [c.a.jira.workflow.DefaultOSWorkflowConfigurator] Could not load class 'com.atlassian.jira.workflow.condition.ValueFieldCondition'
  java.lang.ClassNotFoundException: com.atlassian.jira.workflow.condition.ValueFieldCondition

Environment

Jira Server

Cause

Atlassian integrated most of the Jira Suite Utilities add on (JSU) Workflow Condition/Validator/Post-Functions into their native Jira Cloud Environment. If you perform a migration from Jira Cloud to Jira Server, those Workflow Condition/Validator/Post-Functions do not exist in the default Jira Server Version but can be simply replaced with the JSU Automation Suite for Jira Workflows add-on. The name of the classes are different and needs to be changed in the Workflow XML for it to work properly. It is also possible that, after the migration from Cloud to Server, this add-on was missing in Jira Server and needs to be installed.

Also, note that this type of error can also be caused by any 3rd party add-on which provides workflow conditions, if the whole add-on or the modules with the workflow condition are disabled for this add-on. An example of add-on which might cause this error is JSU Automation Suite for Jira Workflows, but this error might be caused by any other similar add-on.

Resolution

Go to the page ⚙ > Manage Apps > Find new apps, try to install the add-on JSU Automation Suite for Jira Workflows if it's not already installed, add a free trial license and check if the error goes away.

If the error does not go away, go to the page ⚙ > Manage Apps > Manage Apps, and look for any add-on which you already installed in Jira Server, and which provides workflow capabilities (other than the JSU add-on). For each of these add-ons, make sure that the add-on is enabled and that all the modules within this add-on all enabled as well.

If these suggestions do not help, please reach out to Atlassian Support for further assistance.