Usage Problem with TransitionWorkflow Tag due to WorkflowTransitionUtil constraints

Hi,

In our JIRA implementation, we are about to import through Jelly, a large number of issues.
For this import, many of these issues have to progress to their real status (between 6 and 12 status exist depending on concerned workflow).

To do that, I have to generate a set of TransitionWorkflow Tag in Jelly script, for each imported issues.

The problem encountered can be described as follow :

• For example, one issue required to reach the status "MyStatus" following the transitions 10, 20, 30.
• Transitions 10 and 20 contain postFunction which may update some Field or CustomField
• Transition 30 is associated to a screen containing a Field "Timetracking" and "Scheduled Production Date"
• In the normal usage (through Web Interface by the User), these Fields may have been updated through a "Modify" action or during the Transition 30.
• In the import usage (through Jelly), these Fields may have been updated through the previous "CreateIssue" or "AddCustomField" tag.
• And, in both cases, they may have been modified by a Post-Function ...

• In my case, I want assume that the Timetracking has been updated before the Transition 30, then I do not generate any value for it.

  <jira:TransitionWorkflow key="TST-10" user="me" workflowAction="10" />
  <jira:TransitionWorkflow key="TST-10" user="me" workflowAction="20" />
  <jira:TransitionWorkflow key="TST-10" user="me" workflowAction="30" >
     <jira:AddCustomFieldValue name="Scheduled Production Date" value="2006-12-12"/>
  </jira:TransitionWorkflow>

The problem is that WorkflowTransitionUtilImpl.progress() make an update of Fields defined in workflow associated screen, by the value passed in parameters.

• In case of Web Interface usage, theses value are initialize with value in Database, and eventually changed by user enter.
• In case of my Jelly usage, I am not able to provide a value, and then the Timetracking is updated to Null .

The problem occurs with TimeTracking in this case, but we may encouter it in many other cases.

In one word, it would be practice to be able to disengage screen constraints in TransitionWorkflow for Jelly Tags.

Rgds
Vincent