Skip to end of metadata
Go to start of metadata

[2017-08-21] Released Jira Workflow Toolbox 2.2.41


FunctionReturned value
addTime(number base_instant, number offset, string schedule_name, timeZone time_zone) : numberReturns the time instant resulting of adding offset milliseconds to base_instant within schedule with name schedule_name for time_zone timezone.
Example: addTime(2017/12/01 01:00, 8 * {HOUR} + 31 * {MINUTE}, "my_schedule", LOCAL) returns 2017/12/04 10:01.
Example: addTime(2017/12/04 14:00, 2 * {HOUR} + 30 * {MINUTE}, "my_schedule", LOCAL) returns 2017/12/04 17:00.

Since version 2.2.41 negative offset values are supported:
Example: addTime(2017/04/24 09:00, - 2 * {HOUR}, "my_schedule", LOCAL) returns 2017/04/21 14:00.
Example: addTime(2017/04/20 20:30, - 5 * {HOUR}, "my_schedule", LOCAL) returns 2017/04/20 13:00.

In the examples above we have used schedule "my_schedule", whose definition in Schedules Definition Grammar is:

Note that 2017/12/01 is Friday, and 2017/12/04 is Monday.

  • The following numeric fields will be considered as initialized by Fields required or changed validator condition and validator only when returned value is greater than zero:
    • Original estimate
    • Remaining estimate
    • Total time spent
    • Work logged in transition
    • Number of fixed versions
    • Number of affected versions
    • Number of votes received
    • Number of sub-tasks
    • Number of linked issues
    • Number of attachments
    • Number of transition's attachments
    • Number of labels

Bug fixes

  • Post-function Create issues and sub-tasks fails when we have a configuration using an issue type that has been removed from the Jira instance.
  • Functions toNumber() and stringToDate() threw an exception when input parameter was a null instead of a string.