[2015-02-21] Released Jira Workflow Toolbox 2.1.27
New features
- New parser functions:
- nthElement(number list l, number n) : number , returns element at position n in number list l, where n >= 1 and n <= count(l).
- nthElement(string list l, number n) : string , returns element at position n in string list l, where n >= 1 and n <= count(l).
- nthElement(issue list l, number n) : issue list , returns an issue list with the element at position n in issue list l, where n >= 1 and n <= count(l).
- sort(number list l, order) : number list , returns a number list with elements in l sorted in specified order. Available orders are ASC (for ascending order) and DESC (for descending order).
- sort(string list l, order) : string list, returns a string list with elements in l lexicographically ordered. Available orders are ASC (for ascending order) and DESC (for descending order).
- sort(issue list l, field field, order) : issue list , returns an issue list with elements in l* ordered according to values of field. Argument field has format {nnnnn} for numeric and date-time fields, %{nnnnn} for string fields, or %{nnnnn.i} for cascading select fields. Available orders are ASC (for ascending order) and DESC (for descending order).
- isAClone() : boolean , returns true only if current issue is a clone of another issue. An issue is a clone of another issue if it's being created by Jira "Clone" operation, or has issue links of type "clones". This function if useful for bypassing validations in transition Create Issue when the issue is being created by a clonation operation.
- isJwtTriggeredTransition() : boolean , returns true only if current transition execution is being triggered by a Jira Workflow Toolbox post-function. This function is useful for bypassing validations when transition is being non-interactively executed.
- New virtual field "Workflow scheme". Is a text-string field that contains the name of the workflow scheme of the project current issue belongs to.
Improvements
- Post-function " Create issue link" has been substantially improved, in order to make it possible to create issue links between any pair of issues in the Jira instance.
- Added support for Group, Multi-Group and Multi-User fields in conditions "Only users in a field" and "Except users in a field".
- Configuration option "Evaluate all the setting rules" has been made available for field "Labels" in " Set a field as a function of other fields" post-function.
Bug fixes
- Issue #93 - "Only user in custom field" condition didn't work correctly when user was renamed.
- Uncaught "Null Pointer" exception when stringToDate() parser function received as argument a bad formed date string.
- Field code injectors in " Break issue link" post-function didn't contain number and date fields.
- Uncaught exception when reading virtual fields "Reporter's full name" and "Reporter's email" when issue was anonymously reported.
- Minor UI bug and text revision in " Break issue link" post-function configuration screen.
