2013-09-22
Highlights
This is a point release of the add-on adding new add-on capabilities based essentially on version 3.6 of the Appfire Command Line Interface (CLI). Point releases are used for add-ons when improvements warrant that are independent of the ACLI version. This ensures the family based number system continues to indicate the base ACLI version embedded in the add-on.
- 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.
- 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.
New Capabilities
Consistent with similar capabilities pioneered in Create on Transition for Jira and extended with Update on Transition for Jira, given users more options for controlling their workflow.
- Powerful regular expression based pattern matching conditions. These can be used to determine if the CLI action should be run (post function) or the transition should continue (validator).
- Substitution variables for constructing CLI actions or user messaging. Extended to be consistent with related workflow add-ons mentioned above.
- Access to field values from original issue (issue being transitioned)
- Access to field values from parent of original issue
- Access to transition field values (validator)
- JQL query can be used to provide other substitution variables.
Support Latest JIRA Release
- Tested against JIRA 6.1 EAP
Resolved Issues
