Direct download from Marketplace
Improvements
- The Move issues post function now supports parsed text to be used to determine target project, issue type and status selection.
- The Move issues post function now shows custom error message on the screen when issues can't be moved due to incompatibility.
- The expression parser and the field injector now support the Resolution Date.
- The Send an email post function now supports mixed parsing mode when using personalized mode.
New expressions in the parser
Function | Returned Value |
---|---|
setBoolean(string variable_name, boolean value) : 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) : 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) : number | Returns the value stored in a numeric variable named variable_name, which was previously created using the Example: |
setString(string variable_name, string value) : 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) : number list | Creates a variable named variable_name for storing a number list, and assigns it a value, which is also returned in order to be used within an expression. Example: |
getNumberList(string variable_name) : number list | Returns the value stored in number list variable named variable_name, which was previously created using the Example: |
setStringList(string variable_name, string list value) : string list | Creates a variable named variable_name for storing a string list, and assigns it a value, which is also returned in order to be used within an expression. Example: |
getStringList(string variable_name) : string list | Returns the value stored in string list variable named variable_name, which was previously created using the Example: g |
setIssueList(string variable_name, issue list value) : issue list | Creates a variable named variable_name for storing an issue list, and assigns it a value, which is also returned in order to be used within an expression. Example: |
getIssueList(string variable_name) : issue list | Returns the value stored in issue list variable named variable_name, which was previously created using Example: g |
weekOfTheYear(number t, number firstDayOfTheWeek, number minimalDaysInFirstWeek, timeZone time_zone ) : number | Returns the week of the year of the date-time t in a certain time_zone. 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 | Returns the day of the year of date-time t in a certain time_zone, e.g. for January 1st the value returned will be 1. Example: |
timeInValue(string field field, boolean expression predicate) : number | 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) : number | 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) : number | Returns the sum of milliseconds a string field with code %{nnnnn} has had a value satisfying a boolean expression predicate in distinct issues, 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 | 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, 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) : number | 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 ^%. The time being calculated by this function is only counted during a defined schedule with name schedule_name for time_zone timeZone. Example: Example: Example: |
timeInValue(number field field, boolean expression predicate, string schedule_name, timeZone time_zone) : number | 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 ^. The time being calculated by this function is only counted during a defined schedule with name schedule_name for time_zone timeZone. Example: Example: Example: |
timeInValue(string field field issue list issues, boolean expression predicate, string schedule_name, timeZone time_zone) : number | Returns the sum 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 ^%. The time being calculated by this function is only counted during a defined schedule with name schedule_name for time_zone timeZone. Example: Example: Example: |
timeInValue(number field field, issue list issues, boolean expression predicate, string schedule_name, timeZone time_zone) : number | Returns the sum 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 ^. The time being calculated by this function is only counted during a defined schedule with name schedule_name for time_zone timeZone. Example: Example: Example: |
fieldChangeTimes(string field field, boolean expression predicate) : number list | Returns the timestamps 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 ^0%, and after the change by ^1%. The timestamps are returned as a number list sorted in ascending order. Example: Example: Example: |
fieldChangeTimes(number field field, boolean expression predicate) : number list | Returns the timestamps 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 ^0, and after the change by ^1. The timestamps are returned as a number list sorted in ascending order. Example: Example: |
fieldChangeTimes(string field field, issue list issues, boolean expression predicate) : number list | Returns the timestamps of when a string value of fields 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 ^0%, and after the change by ^1%. The timestamps are returned as a number list containing a sequence of sorted numeric values in ascending order for each parameter issue. Example: Example: Example: |
fieldChangeTimes(number field field, issue list issues, boolean expression predicate) : number list | Returns the timestamps of when a numeric value of fields 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 ^0, and after the change by ^1. The timestamps are returned as a number list containing a sequence of sorted numeric values in ascending order for each parameter issue. Example: Example: |
lastFieldChangeTime(string field field) : number | Returns the timestamp of most recent value update of a field with code %{00000}. Example: |
unreleasedVersionsBySequence() : string list | Returns a string list 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() : string list | Returns a string list 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. |
Bug fixes
- Using the Move issues post function on individual sub-tasks (without moving the parent) resulting resulted in incompatible parent-child relationships. Moving individual sub-tasks is currently not available.
- Issues were not correctly moved to newly created Epics.
- Custom fields could be set to values not available/valid in their respective field context using the Move issues post function.
- Setting the "Sprint ID" to a value equal or greater than 1000 produced an error.
- Incorrect error messages were logged when detecting deleted custom fields.