Symptoms

Users are unable to transition an issue after restoring JIRA 3.x backup data to JIRA 4.x. The following screenshot shows the error when transitioning an issue in JIRA 4.x:

The following appears in the atlassian-jira.log:

2010-11-09 17:31:46,809 http-8080-5 ERROR admin 1051x309x1 1gnjn27 0:0:0:0:0:0:0:1 /secure/CommentAssignIssue.jspa [atlassian.jira.workflow.SimpleWorkflowManager\] An exception occurred
java.lang.IllegalArgumentException: Unable to find field 'customfield_10000'
at com.googlecode.jsu.util.WorkflowUtils.getFieldFromKey(WorkflowUtils.java:94)
at com.googlecode.jsu.workflow.function.ClearFieldValuePostFunction.executeFunction(ClearFieldValuePostFunction.java:28)
at com.googlecode.jsu.workflow.function.AbstractPreserveChangesPostFunction.execute(AbstractPreserveChangesPostFunction.java:58)
...

Cause

This is caused by a configuration in the JIRA Suite Utilities plugin.

In JIRA 3.x, if there's a workflow transition containing a Clear Field Value post function (JIRA Suite Utilities) to purge the Resolution Date custom field (JIRA Charting Plugin), this will cause a problem when migrating the 3.x backup data to JIRA 4.x. The problem occurs because in JIRA 4.x, the Resolution Date has become a system field under the name Resolved, therefore the Clear Field Value post function couldn't find the Resolution Date custom field thus producing the stated error when executing the particular transition, assuming that the Resolution Date field is missing. Attached below are screenshots which describe the cause of the error:

JIRA 3.x

A post function has been set to purge the Resolution Date custom field:

JIRA 4.x

What should be the purge field value post function has changed which might seem to be duplicating the above post function. This is root cause of the problem:

Resolution

Reconfigure the problematic transition, by removing the incorrect post function and replace it to purge the Resolved field should do the trick, as shown below: