This is critical for the workflow in JIRA Studio; we cannot proceed without it.

To reproduce:

1. Create a new workflow (not by copying, but instead by typing a name and description). You can add steps if you like, but that won't matter.
2. Create a new scheme and assign the workflow to that scheme
3. create a new project
4. assign the scheme to that project
5. try to create an issue in that project. You get the following stack trace:

ava.lang.NullPointerException at com.opensymphony.workflow.util.DefaultVariableResolver.translateVariables(DefaultVariableResolver.java:73) at com.opensymphony.workflow.AbstractWorkflow.createNewCurrentStep(AbstractWorkflow.java:1467) at com.opensymphony.workflow.AbstractWorkflow.transitionWorkflow(AbstractWorkflow.java:1256) at com.opensymphony.workflow.AbstractWorkflow.initialize(AbstractWorkflow.java:618) at com.atlassian.jira.workflow.SimpleWorkflowManager.createIssue(SimpleWorkflowManager.java:217) at com.atlassian.jira.issue.managers.DefaultIssueManager.createIssue(DefaultIssueManager.java:378) at com.atlassian.jira.issue.managers.DefaultIssueManager.createIssue(DefaultIssueManager.java:326) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
....
....
....

Cause:
The ActionDescriptor's unconditional result's old status is null, but opensymphony tries to access it.

Possible solution:
Ensure this is set to somethign non-null by default.