Admins are able to delete active workflow schemes, potentially resulting in data corruption

Admins are able to delete active workflow schemes, which would cause the associated workflows to appear inactive, opening the possibility to having an active workflow being deleted, resulting in issues that have no transitions or transitions that are incorrect. You will probably see in the logs:

• Some warnings like:

  2012-08-29 14:30:08,476 http-bio-8090-exec-10 ERROR admin 869x18070x1 k49von 172.20.9.76 /browse/MKY-2 [atlassian.jira.workflow.IssueWorkflowManagerImpl] State of issue [MKY-2] has an action [id=11] which cannot be found in the workflow descriptor
  2012-08-29 14:30:08,476 http-bio-8090-exec-10 ERROR admin 869x18070x1 k49von 172.20.9.76 /browse/MKY-2 [atlassian.jira.workflow.IssueWorkflowManagerImpl] State of issue [MKY-2] has an action [id=21] which cannot be found in the workflow descriptor
  2012-08-29 14:30:08,476 http-bio-8090-exec-10 ERROR admin 869x18070x1 k49von 172.20.9.76 /browse/MKY-2 [atlassian.jira.workflow.IssueWorkflowManagerImpl] State of issue [MKY-2] has an action [id=41] which cannot be found in the workflow descriptor
  2012-08-29 14:33:03,579 http-bio-8090-exec-17 ERROR admin 870x18295x1 k49von 172.20.9.76 /browse/MKY-2 [atlassian.jira.workflow.IssueWorkflowManagerImpl] State of issue [MKY-2] has an action [id=11] which cannot be found in the workflow descriptor
  2012-08-29 14:33:05,850 http-bio-8090-exec-17 ERROR admin 870x18295x1 k49von 172.20.9.76 /browse/MKY-2 [atlassian.jira.workflow.IssueWorkflowManagerImpl] State of issue [MKY-2] has an action [id=21] which cannot be found in the workflow descriptor
  2012-08-29 14:33:08,013 http-bio-8090-exec-17 ERROR admin 870x18295x1 k49von 172.20.9.76 /browse/MKY-2 [atlassian.jira.workflow.IssueWorkflowManagerImpl] State of issue [MKY-2] has an action [id=41] which cannot be found in the workflow descriptor
  

• Exceptions like:

  2012-08-29 14:44:07,202 http-bio-8090-exec-15 ERROR admin 883x463x1 x4ixsb 172.20.9.76 /browse/MKY-2 [opensymphony.workflow.basic.BasicWorkflow] Error checking available actions
  com.opensymphony.workflow.FactoryException: Unknown workflow name
          at com.opensymphony.workflow.config.DefaultConfiguration.getWorkflow(DefaultConfiguration.java:92)
          at com.opensymphony.workflow.AbstractWorkflow.getAvailableActions(AbstractWorkflow.java:77)
          at com.atlassian.jira.workflow.IssueWorkflowManagerImpl.getAvailableActionIds(IssueWorkflowManagerImpl.java:140)
          at com.atlassian.jira.workflow.IssueWorkflowManagerImpl.getAvailableActions(IssueWorkflowManagerImpl.java:41)
          at com.atlassian.jira.workflow.IssueWorkflowManagerImpl.getSortedAvailableActions(IssueWorkflowManagerImpl.java:65)
          at com.atlassian.jira.issue.transitions.TransitionLinkFactory.getAvailableActions(TransitionLinkFactory.java:63)
          at com.atlassian.jira.issue.transitions.TransitionLinkFactory.getLinks(TransitionLinkFactory.java:52)
          at com.atlassian.jira.plugin.webfragment.DefaultSimpleLinkManager.getLinks(DefaultSimpleLinkManager.java:190)
          at com.atlassian.jira.plugin.webfragment.DefaultSimpleLinkManager.getLinksForSection(DefaultSimpleLinkManager.java:124)
          at com.atlassian.jira.issue.util.IssueOperationsBarUtil.getLinksForSection(IssueOperationsBarUtil.java:208)
          at com.atlassian.jira.issue.util.IssueOperationsBarUtil.getPromotedLinks(IssueOperationsBarUtil.java:105)  <+3> (NativeMethodAccessorImpl.java:39) (DelegatingMethodAccessorImpl.java:25)
          at java.lang.reflect.Method.invoke(Method.java:597)
          at webwork.util.InjectionUtils$DefaultInjectionImpl.invoke(InjectionUtils.java:70)
          at webwork.util.InjectionUtils.invoke(InjectionUtils.java:56)
          at webwork.util.ValueStack.findValue(ValueStack.java:514)
          at webwork.util.ValueStack.findValue(ValueStack.java:213)
          at webwork.view.taglib.WebWorkBodyTagSupport.findValue(WebWorkBodyTagSupport.java:62)
          at webwork.view.taglib.BasicPropertyTag.doStartTag(BasicPropertyTag.java:54)
          at org.apache.jsp.includes.panels.issue.viewissue_002dopsbar_jsp._jspx_meth_ww_005fproperty_005f6(viewissue_002dopsbar_jsp.java:535)
  

You should be able to fix this by migrating that project onto a new workflow scheme. You cannot use the default workflow scheme.