1. A substitution variable incompatibility was introduced in this release due to the introduction of the substitution variables shared with other similar workflow add-ons. Previous use of pattern1_1 and similar should be changed to cli_pattern1_1 and similar. The pattern1_n and pattern2_n variables now refer to the conditioning patterns.
2. A substitution variable incompatibility was introduced in this release due to shared processing with other similar workflow add-ons. Unqualified references to custom field names or id now represent parent values and NOT the value from the original issue (the issue being transitioned). These values are the same if the original issue is not a subtask, but could be different if it is. It is highly recommended to discontinue use of unqualified custom field references due to the ambiguity of this rather poor design decision. Clearly specifying %original_...% or %parent_...% is better for future maintenance of the post functions.

Sorry for the inconvenience. Having consistent behavior with the other add-ons will make it easier for future use and in this case required the incompatibility.