[2015-05-08] Released JIRA Workflow Toolbox 2.1.31
New features
- New post-function "Clone issue links": it imports issue links from cloned issue. When added to "Create Issue" transition, this post-function ensures that issue links will always be cloned, even if the user forgets to check "Clone Links" checkbox.
- New very powerfull filtering functions have been added to the parser:
| FUNCTION | RETURNED VALUE |
|---|---|
| filterByPredicate(issue list l, boolean expression predicate) : issue list | Returns a list with issues in l that validate predicate. Argument predicate is a boolean expression, where references to field values in l are done using prefix ^ for field codes. Examples of field references: ^%{00000} is field code for Summary, and ^{00068} is field code for Original estimate of issues in argument l. Examples of usage: filterByPredicate(subtasks(), ^%{00094} in %{00094}) returns the list of subtasks with selected Components in current issue's selected components. filterByPredicate(linkedIssues("blocks"), %{00028} = null AND ^{00017} < {00017}) returns the list of unresolved blocked issues with priority higher than current issue's priority. |
| filterByPredicate(number list l, boolean expression predicate) : number list | Returns a list with numbers in l that validate predicate. Argument predicate is a boolean expression, where ^ is used for referencing numeric values in argument l. Examples: filterByPredicate([1, 2, 3, 4], ^ > 2) returns values greater than 2, i.e., [3, 4] filterByPredicate([1, 2, 3, 4], remainder(^, 2) = 0) returns even values, i.e., [2, 4] |
| filterByPredicate(string list l, boolean expression predicate) : string list | Returns a list with strings in l that validate predicate. Argument predicate is a boolean expression, where ^% is used for referencing string values in argument l. Examples: filterByPredicate(["book", "rose", "sword"], length(^%) > 4) returns ["sword"]. filterByPredicate(["book", "rose", "sword"], ^% in %{00000} OR ^% in %{00001}) returns a list with those strings in first argument that also appear in issue Summary or Description. |
Improvements
- Added support for filtering by field values to the following features:
- Condition on linked issues
- Condition on subtasks
- Condition on a list of issue keys
- Validation on linked issues
- Validation on subtasks
- Validation on a list of issue keys
- Write field on linked issues or subtasks
- Read fields from linked issues or subtasks
- Configuration screens revised for improved understandability in the following features:
- Condition on linked issues
- Condition on subtasks
- Condition on a list of issue keys
- Validation on linked issues
- Validation on subtasks
- Validation on a list of issue keys
- Added support for groups to " Add or remove watchers" post-function.
- Support "Sprint" the JIRA Agile's custom field.
Bug fixes
- Virtual field "Transition's attachments" and "Transition's attachments with details" were failing in certain circumstances since JIRA 6.4.
- Parser function "filterByNumericFieldValue()" failed when there are some issue to be filtered with non-initialized fields.
- Parser function "transitivelyLinkedIssues()" didn't include in its output issues directly linked to current issue, as it was supposed.
- Minor UI failures.
