[2017-03-08] Released Jira Workflow Toolbox 2.2.33
New features
- New parser functions:
Function | Returned value |
---|---|
leastBusyUserInRole(string projectRoleName, string projectKey, string jqlQuery) : string | Equivalent to the previous function but with extra argument jqlQuery, used for restricting the issues to be considered to pick the least busy user. Example: leastBusyUserInRole("Developers", %{00018}, "project = " + %{00018}) returns the user playing role Developers in current project, with the least number of unresolved issues in current project assigned. Note that %{00018} is field code for Project key. |
nextUserInGroup(string groupName, string queueName) : string | returns the name of the next active user in group with name groupName, for a round-robin queue with name queueName. The string queueName is an arbitrary name. The queue is automatically created the first time a queue is used in a function call. Each time the function is called on the same pair of arguments (group, queue), a different user in the group is returned. The queue can be used in different transitions of the same or different workflows within the same Jira instance. Example: nextUserInGroup("jira-developers", "code-review-queue") returns the username of the next user in group jira-developers for round-robin queue code-review-queue. Each time the function is called with the same pair of arguments, a different username is returned. |
- Included round-robin algorithm as an option for Assign to project role:
Improvements
- New parameter JQL Query in post-function Assign to project role for restricting issues to be considered when assigning to the least busy user in a project role:
- Performance improvement in functionality for selecting the least busy user in a project role, either using post-function Assign to project role or function
leastBusyUserInRole()
.
Bug fixes
- Issue #499 - Post-function Create issues and sub-tasks doesn't check whether selected issue type is valid for selected project
- Issue #534 - Virtual field Target status doesn't work on "Create Issue" transitions
- Issue #536 - Problems with
lastAssigneeInRole()
function and the parser's documentation