Blog from June, 2018

Decadis AG posted on Jun 29, 2018
JWT Release Notes 2.4.5

[2018-06-29] Released Jira Workflow Toolbox 2.4.5

Direct download from Marketplace

Bug fixes

  • Certain post functions are either not displaying correctly or are not editable after adding them initially. 

  • Affected post functions:

    • Add or disable option in Cascading Select field

    • Add or disable option in Select List, Radio Button, Multi-Select List or Checkbox field

    • Copy or add custom field value to issue description

    • Log work

    • Parse field for extracting data

    • Set or create a user property

    • Copy Cascading Select field

    • Cascading select comparer

Find more Release Notes in our Version History section.

Decadis AG posted on Jun 21, 2018
JWT Release Notes 2.4.4

[2018-06-21] Released Jira Workflow Toolbox 2.4.4

Direct download from Marketplace

New features

  • New Parser function: timeInStatus() - easily identify how much time issues spend in a specific status. The function comes with four distinct configuration options to meet your specific needs. If used in a calculated field you might want to try to format the output as a duration as opposed to a number to improve readability.


timeInStatus(string status_name) : number
Available since version 2.4.4

Returns the number of milliseconds the current issue has remained in a status with name status_name. If an issue has been in that status more than once, then duration will be summed up and the total time spent in the status will be returned.

Example: timeInStatus("Open") returns the number of milliseconds the current issue has stayed in status "Open".

In order to display this value in a more readable way, the milliseconds should be transformed into a more readable unit, like in the following example:

timeInStatus("Open") / {DAY} - for number of days, or timeInStatus("Open") / {HOUR} - for number of hours

timeInStatus(string status_name, string schedule_name, timeZone time_zone) : number
Available since version 2.4.4

Returns the number of milliseconds the current issue has remained in a status with name status_namewithin a schedule named schedule_name for a given time_zone timeZone. If an issue has been in that status more than once, then duration will be summed up and the total time spent in the status will be returned.

Example: timeInStatus("Open", "my_schedule", LOCAL) returns the number of milliseconds the current issue has stayed in status "Open" within the schedule called "my_schedule" matching the server's default timeZone.

timeInStatus(string status_name, issue list issues) : number
Available since version 2.4.4

Returns the sum of milliseconds issues in an issue list issues have remained in a status with namestatus_name. If an issue from that list has been in that status more than once, then duration will be summed up and the total time spent in the status will be returned.

Example: timeInStatus("Open", subtasks()) returns the number of milliseconds the current issue's sub-tasks have stayed in status "Open".

timeInStatus(string status_name, issue list issues, string schedule_name, timeZone time_zone) : number
Available since version 2.4.4

Returns the sum of milliseconds issues in an issue list issues have remained in a status with namestatus_name within a schedule named schedule_name for a given time_zone timeZone. If an issue from that list has been in that status more than once, then duration will be summed up and the total time spent in the status will be returned.

Example: timeInStatus("Open", subtasks(), "my_schedule", LOCAL) returns the number of milliseconds the current issue's sub-tasks have stayed in status "Open" within the schedule called "my_schedule" matching the server's default timeZone.



Check out the official documentation for more details.

Bug fixes

  • Configuration parameter "Evaluate all the setting rules" on "Set a field as a function of other fields" post function is disabled on "Ephemeral string" fields
  • "linkedIssues()" parser function stopped working properly in version 2.4.3
  • "Create issues and sub-tasks" post function is not correctly setting the components in other projects


Find more Release Notes in our Version History section.


Decadis AG posted on Jun 13, 2018
JWT Release Notes 2.4.3

[2018-16-13] Released Jira Workflow Toolbox 2.4.3

Direct download from Marketplace

Bug fix

Find more Release Notes in our Version History section.

Decadis AG posted on Jun 11, 2018
JWT Release Notes 2.4.2

[2018-06-11] Released Jira Workflow Toolbox 2.4.2

Direct download from Marketplace

This major release replaces version 2.4.1 which introduced a bug in the Send an email post function.

New Features

  • The email's priority and BCC recipients can now be configured in the "Send an email" post function.
  • Specify the location of the "Message to show when validation fails". The message can be shown next to any field or at the top of the transition screen.
  • Insight custom fields are now supported up to version 5.4. New custom fields will be supported in upcoming releases.
  • The "Update issue fields" post function now supports the Portfolio Team field.
  • You can now update Service Desk specific fields through JWT post functions:
    • Customer Request Type
    • Organizations
    • Customer Request Channel

Improvements

  • Major Javascript performance improvements

Bug fixes

  • Calculated fields occasionally prevent the execution of built-in issue actions (e.g. move/delete issues).
  • Parent's Virtual fields cannot be set using "Update issue fields" post function in standard mode.

Find more Release Notes in our Version History section.


Decadis AG posted on Jun 07, 2018
JWT Release Notes 2.4.1

[2018-06-07] Released Jira Workflow Toolbox 2.4.1

This version has been replaced with version 2.4.2, because it introduced a bug in the Send an email post function.

New Features

  • Both an email's priority and the BCC recipients can now be configured in the Send an email post function.
  • Specify the location of the "Message to show when validation fails". The message can be shown next to any field or at the top of the transition screen.
  • Insight custom fields are now supported up to version 5.4. New Insight custom fields will be supported in the upcoming release.
  • The "Update issue fields" post function now supports the Portfolio Team field.
  • You can now update Service Desk specific fields through JWT post functions:
    • Customer Request Type
    • Organizations
    • Customer Request Channel

Improvements

  • Javascript performance has been improved for all JWT functions.

Bug fixes

  • Exceptions thrown by calculated fields occasionally prevent the execution of built-in issue actions (e.g. move issue, delete issue).
  • Parent's Virtual fields couldn't be set using Update issue fields post function in standard mode.

Find more Release Notes in our Version History section.