[2015-07-23] Released Jira Workflow Toolbox 2.1.33
New features
- New " Parse field for extracting data" post-function: allows extracting pieces of information from the content of a field using delimiter marks, or specifying a certain format for the value to be extracted.
- New virtual fields: "Last commenter" and "Parent's last commenter" for retrieving the user who entered the last comment in current issue or parent issue.
- Added new function to the plugin's parser:
| FUNCTION | RETURNED VALUE |
|---|---|
| issuesFromJQL(string jql_query) : issue list | Returns the list of issues resulting of the execution of a JQL query represented by string argument jql_query. Visibility permissions applied are those of current user. We advice to use this function for performance reasons when the number of issues to be retrieved or filtered is very high (all issues in a project or various projects). Typically you will want to use this function for replacing any current expression using getIssuesFromProjects() function. |
| issuesFromJQL(string jql_query, string user_name) : issue list | Returns the list of issues resulting of the execution of a JQL query represented by string argument jql_query. Visibility permissions applied are those of user in argument user_name. We advice to use this function for performance reasons when the number of issues to be retrieved or filtered is very high (all issues in a project or various projects). Typically you will want to use this function for replacing any current expression using getIssuesFromProjects() function. |
| filterByStatusCategory(issue list issues, string status_categories) : issue list | Filters issue list in argument issues, leaving only those ones in statuses with categories in status_categories. Argument status_categories is a comma separated list of status category names. Example: filterByStatusCategory(linkedIssues("is blocked by"), "New, In Progress") returns the list of blocking issues in statuses with categories New or In Progress. |
| filterByProjectCategory(issue list issues, string project_categories) : issue list | Filters issue list in argument issues, leaving only those ones in projects with category in project_categories. Argument project_categories is a comma separated list of project category names. Example: filterByProjectCategory(linkedIssues(), "Development, Production") returns the list of linked issues belonging to projects in categories keys Development or Production. |
| allComments() : string list | Returns a string list with all the comments in current issue in ascension order by creation date. |
| allComments(issue list l) : string list | Returns a string list with all the comments in issues in l, ordered by aparition order in l and by creation date in ascension order. Example: allComments(issueKeysToIssueList(%{00041})) returns parent issue's comments, where %{00041} is field code for parent issue's keys. |
| allCommenters() : string list | Returns a string list with the user names of comment authors and updaters in current issue. |
| allCommenters(issue list l) : string list | Returns a string list with the user names of comment authors and updaters of issues in l. Example: allCommenters(issueKeysToIssueList(%{00041})) returns a list with all the commenters and comment updaters for parent issue, where %{00041} is field code for parent issue's keys. |
| dateTimeToString(number t, string date_time_pattern, language) : string | Returns a string representing the date-time value at t with a certain custom format defined by date_time_pattern string parameter, using a certain language when using words for months, days of the week, etc. This function is useful in post-function
Copy parsed text to a field to represent as a string the result of a time expression. Example: dateTimeToString(2011-03-25 11:30, "yyyy.MM.dd 'at' HH:mm:ss", USER_LANG) returns string "2011.03.25 at 11:30:00". |
| stringToDate(string s, string date_time_pattern) : number | returns a numeric value with the date-time represented by string s. Expected format of value at parameter "s" is defined by date_time_pattern string parameter. The numeric value returned corresponds to the milliseconds elapsed since January 1, 1970, 00:00:00 GMT. Example: stringToDate("2011.03.25 at 11:30:00", "yyyy.MM.dd 'at' HH:mm:ss") returns a date-time numeric value that can be used for setting a Date Time picker custom field. |
Improvements
- Minor UI improvements: some labels are made clickable, and improved editor has been added to "Write field on issues returned by JQL query" and " Read Field From Issues Returned By JQL Query" post-functions.
- Support for setting custom fields "Account" and "Team" provided by Tempo Timesheet add-on. Values used for setting these fields are internal numerical IDs. These Ids can be found out tempo_timesheet_internal_ids.png.
- Added support for Project Picker custom fields to parser functions: numberOfSelectedItems(), numberOfAvailableItems() and availableItems().
Bug fixes
- Issue #139: Inactive user is able to post comments
- Issue #150: Error in "Transition's attachments" virtual field introduced in version 2.1.31.
- Transition execution on foreign issues by means of writing into fields "Issues status", "Issue status (delayed writing)", "Execute transition" and "Execute transition (delayed execution)" sometimes are done out of order and fail when a high number of transitions are committed to the same issue in a very short period of time (as bursts).
- Fixed minor bugs in the following parser functions: replaceFirst(), replaceAll(), matches(), findAndReplace(), getCertainVersion(), findByRegexp().
- Issue #145 and #152: Parameter "Run as", introduced in version 2.1.32, was causing very long configuration screen load times for features where it was introduced. This problem only appeared in instances of Jira with a very high number of users.
- Parameter "Run as" didn't work in "Clone issue links".
