SOAP and Jelly Progress Workflow calls do not take into account exisiting issue values

If SOAP or the TransitionWorkflow Jelly tag is use to progress and issue through a workflow step, then the existing issue values can be ignored n the process.

This is related to JRA-16112 and JRA-16859 which are attempts to make Resolution field act like it does on the web page.

This issue is a placeholder for the work needed to fix this and more importantly test it up the wazoo.

In a nutshell the SOAP and Jellt tags need to populate the FieldHolderValues map before calling WorkflowTransitionUtil.

However the big guy is afraid that the objects a custom field places into the FHV on populateFromIssue() may NOT be the same objects that are placed into the FHV via populateFromParams()

And hence this could lead to class cast exceptions and the like.

We need to re-implement Dylans change JRA-16112 with the populateFromIssue() call and then a bucket load of testing on All the field and all the CustomField types to prove that no problems will arise in the possible populateFromIssue()/populateFromParams() mismatch.