Blog
Final release
Automation Toolbox for Jira is going to be fully integrated into Jira Workflow Toolbox (JWT) making 1.1.1 the final standalone release.
Take your processes to the next level!
We are excited to announce that Automation Toolbox for Jira (ATJ) will soon be fully integrated into our top-rated app Jira Workflow Toolbox (JWT).
Direct download from Marketplace
Improvements
- An improved user interface for importing rules
Bug fixes
- Improved display behavior of multiple forms
- The IN operator can now be used with the new field code syntax
Find more release notes in our Version History section
Data Center approved
This is the first Atlassian approved Data Center compatible version of Automation Toolbox for Jira.
New features
- Manual trigger to configure rules that are executed manually
- Log Work action to create automatic work logs
- Create Issue Link action to create issue links, choosing the issue link type and issues to be linked to
- Delete Issue Link action to delete issue links, optionally filtering by issue link type(s) and/or custom issue selection
- Possibility to import and export rules
Improvements
- Added the possibility to search by the field id's in the field injector drop-down
- New style for the expressions of the elements in the rule view
- Added confirm dialog to close the rule sidebar if the configuration has been changed
- Added Run now button to Actions menu of activated Scheduled Rules in the Automation Rules view
- Added the possibility to set and inherit issue links in the Create Issue action
- Added the possibility to inherit issue fields in the Create Issueaction
- Improved the view of the inherit fileds option in the Create Issue action
- General UI improvements in rule sidebar and updated descriptions
Bug fixes
- User selectors were broken, if the selected user was renamed
- Seed issue was mistakenly displayed in the Create Issue action
- User condition used to throw a Nullpointer when trying to check against required Selected user(s)
- Syntax highlighting didn't work for the cascading field key when a value of a cascading list was selected
- Cascading fields didn't work properly
- Removed Seed issue option from the issue selection in the Create Issue action
Direct download from Marketplace
New expressions in the parser
| Function | Input | Output |
|---|---|---|
| setBoolean(string variable_name, boolean value) | STRING BOOLEAN | Creates a variable named variable_name for storing a BOOLEAN value, and assigns it a value, which is also returned in order to be used within an expression. Example: |
| getBoolean(string variable_name) | BOOLEAN | Returns the value stored in a BOOLEAN variable named variable_name, which was previously created using the Example: |
| setNumber(string variable_name, number value) | STRING NUMBER | Creates a variable named variable_name for storing a NUMBER, and assigns it a value, which is also returned in order to be used within an expression. Example: |
| getNumber(string variable_name) | STRING NUMBER | Returns the NUMBER value stored in a numeric variable named variable_name, which was previously created using the Example: |
| setString(string variable_name, string value) | STRING STRING | Creates a variable named variable_name for storing a STRING, and assigns it a value, which is also returned in order to be used within an expression. Example: |
| getString(string variable_name) | STRING | Returns the value stored in STRING variable named variable_name, which was previously created using the Example: |
| setNumberList(string variable_name, number list value) | STRING NUMBER [] | Creates a variable named variable_name for storing a NUMBER [], and assigns it a value, which is also returned in order to be used within an expression. Example: |
| getNumberList(string variable_name) | STRING | Returns the value stored in NUMBER [] variable named variable_name, which was previously created using the Example: |
| setStringList(string variable_name, string list value) | STRING STRING [] | Creates a variable named variable_name for storing a STRING [], and assigns it a value, which is also returned in order to be used within an expression. Example: |
| getStringList(string variable_name) | STRING | Returns the value stored in STRING [] variable named variable_name, which was previously created using the Example: |
| setIssueList(string variable_name, issue list value) | STRING ISSUE [] | Creates a variable named variable_name for storing an ISSUE [], and assigns it a value, which is also returned in order to be used within an expression. Example: |
| getIssueList(string variable_name) | STRING | Returns the value stored in ISSUE [] variable named variable_name, which was previously created using Example: |
weekOfTheYear(number t, number firstDayOfTheWeek, number minimalDaysInFirstWeek, timeZone time_zone ) | NUMBER NUMBER NUMBER TIMEZONE | Returns the week of the year of the date-time t in a certain time_zone as NUMBER. The parameter firstDayOfTheWeek represents the first day of the week, e.g.: {SUNDAY} in the U.S., and {MONDAY} in Germany. The parameter minimalDaysInFirstWeek represents the minimal number of days required in the first week of the year, e.g., if the first week is defined as the one that contains the first day of the first month of the year, value 1 should be used. If the minimal number of days required must be a full week (e.g. all days of the week need to be in that year), value 7 should be used. Example: Example: Example: |
| dayOfTheYear(number t, timeZone time_zone) | NUMBER TIMEZONE | Returns the day of the year of date-time t in a certain time_zone as NUMBER, e.g. for January 1st the value returned will be 1. Example: |
timeInValue(string field field, boolean expression predicate) | STRING BOOLEAN | Returns the NUMBER of milliseconds a string field with code %{nnnnn} of the current issue has had a value satisfying a boolean expression predicate, where the string value of the field with code %{nnnnn} is represented by Example: Example: Example: timeInValue(%{00017}, ^% in ["Critical", "High"]) returns the number of milliseconds the field priority (field code %{00017}) of the current issue has had a value of Critical or High. |
timeInValue(number field field, boolean expression predicate) | NUMBER BOOLEAN | Returns the NUMBER of milliseconds a number or date-time field with code {nnnnn} of the current issue has had a value satisfying a boolean expression predicate, where the numeric value of the field with code {nnnnn} is represented by Example: Example: Example: |
timeInValue(string field field, issue list issues, boolean expression predicate) | STRING ISSUE [] BOOLEAN | Returns the sum of milliseconds a string field with code %{nnnnn} has had a value satisfying a boolean expression predicate in distinct issues as NUMBER, where the string value of the field with code %{nnnnn} is represented by Example: Example: Example: |
timeInValue(number field field, issue list issues, boolean expression predicate) | NUMBER ISSUE [] BOOLEAN | Returns the sum of milliseconds a number or date-time field with code {nnnnn} has had a value satisfying a boolean expression predicate in distinct issues as NUMBER, where the numeric value of the field with code {nnnnn} is represented by ^.Example: Example: Example: |
timeInValue(string field field, boolean expression predicate, string schedule_name, timeZone time_zone) | STRING BOOLEAN STRING TIMEZONE | Returns the NUMBER of milliseconds a string field with code %{nnnnn} of the current issue has had a value satisfying a boolean expression predicate, where the string value of the field with code %{nnnnn} is represented by Example: Example: Example: |
timeInValue(number field field, boolean expression predicate, string schedule_name, timeZone time_zone) : number | NUMBER BOOLEAN STRING TIMEZONE | Returns the NUMBER of milliseconds of a number or date-time field with code {nnnnn} of the current issue has had a values satisfying a boolean expression predicate, where the numeric value of the field with code {nnnnn} is represented by Example: Example: Example: |
timeInValue(string field field,issue list issues, boolean expression predicate, string schedule_name, timeZone time_zone) | STRING ISSUE [] BOOLEAN STRING TIMEZONE | Returns the NUMBER of milliseconds a string field with code %{nnnnn} has had a value satisfying a boolean expression predicate in distinct issues, where the value of the field with code %{nnnnn} is represented by Example: Example: Example: |
timeInValue(number field field, issue list issues, boolean expression predicate, string schedule_name, timeZone time_zone) | NUMBER ISSUE [] BOOLEAN STRING TIMEZONE | Returns the NUMBER of milliseconds number or date-time field with code {nnnnn} has had a value satisfying a boolean expression predicate in distinct issues, where the numeric value of the field with code {nnnnn} is represented by Example: Example: Example: |
fieldChangeTimes(string field field, boolean expression predicate) | STRING BOOLEAN | Returns the timestamps as NUMBER [] of when a string value of field with code %{nnnnn} has changed satisfying a certain predicate that depends on the values of the field before and after the value change. The string value before the change is represented by Example: Example: Example: |
fieldChangeTimes(number field field, boolean expression predicate) | NUMBER BOOLEAN | Returns the timestamps as NUMBER [] of when a numeric / date-time value of field with code {nnnnn} has changed satisfying a certain predicate that depends on the values of the field before and after the value change. The numeric value before the change is represented by Example: Example: |
fieldChangeTimes(string field field, issue list issues, boolean expression predicate) | STRING ISSUE [] BOOLEAN | Returns the timestamps as NUMBER [] of when a string value of field with code %{nnnnn} in distinct parameter issues have changed satisfying certain predicate that depends on the values of the fields before and after the value change. The string value before the change is represented by Example: Example: Example: |
fieldChangeTimes(number field field, issue list issues, boolean expression predicate) | NUMBER ISSUE [] BOOLEAN | Returns the timestamps as NUMBER [] of when a numeric value of field with code {nnnnn} in distinct parameter issues have changed satisfying a certain predicate that depends on the values of the fields before and after the value change. The numeric value before the change is represented by Example: Example: |
| lastFieldChangeTime(string field field) | STRING | Returns the timestamp as NUMBER of most recent value update of a field with code %{nnnnn}. Example: |
| unreleasedVersionsBySequence() | Returns a STRING [] with the unreleased versions in the current project with the default order. Only non-archived versions are returned. The first version in the list is the lowermost version in the version table. | |
| releasedVersionsBySequence() | Returns a STRING [] with the released versions in the current project with the default order. Only non-archived versions are returned. The first version in the list is the lowermost version in the version table. |
Find more release notes in our Version History section.
