Introducing the new JWT expression editor! Have all control in a single place when customizing workflows and writing JWT and Jira expressions.

New features:

• New intuitive guided configuration with the central field injector, more built-in examples and auto-completion
• Support of a large set of new parser functions like count() and subtasks() to access and manipulate issue data
• Live testing of expressions against any issue without having to publish the workflow
• A new in-app handbook and function reference to copy&paste or mark your favorites

Find out more in our revamped documentation!

Compatibility

• Added support for Jira 8.12

Improvements

• Access the internal ID of your Jira projects by using projectIDFromKey() either as a field code or parser function
• Access the sprint completion date through a brand new field code
• The function usersWithEmail() now ignores the case which makes it easier to find the users you are looking for
• Smart improvements in terms of logging and security

Bug fixes

• The function timeInStatus() returned wrong results in case an issue was never transitioned
• The functions fieldHistory() and previousValue() returned unexpected results for user picker fields
• Improvements to the Automation Rules configuration

Compatibility

• Added support for Jira 8.12

Improvements

• Access the internal ID of your Jira projects by using projectIDFromKey() either as a field code or parser function
• Access the sprint completion date through a brand new field code
• The function usersWithEmail() now ignores the case which makes it easier to find the users you are looking for
• Smart improvements in terms of logging and security

Bug fixes

• The function timeInStatus() returned wrong results in case an issue was never transitioned
• The functions fieldHistory() and previousValue() returned unexpected results for user picker fields
• Improvements to the Automation Rules configuration

Bug fix

• Expression parser fields were broken in 2.9.1 when editing some workflow functions

Bug fix

• Expression parser fields were broken in 2.9.1 when editing some workflow functions

Improvements

• Extended support for Botron's Configuration Manager, now including versions, components and custom field options
• The child level of cascading selects fields is now validated as required only when there are child options available
• Added warning in case of configuring self-referencing expressions in calculated custom fields
• Minor UI updates

Bug fixes

• The selected transition could be cleared unintentionally when editing a Transition issues post function
• Parent fields were not avaible in the Field Changed Event trigger

Improvements

• Extended support for Botron's Configuration Manager, now including versions, components and custom field options
• The child level of cascading selects fields is now validated as required only when there are child options available
• Added warning in case of configuring self-referencing expressions in calculated custom fields
• Minor UI updates

Bug fixes

• The selected transition could be cleared unintentionally when editing a Transition issues post function
• Parent fields were not avaible in the Field Changed Event trigger

🆕 JWT now includes automation rules! 🆕

A year ago we released our app Automation Toolbox to not only enable you to automate your daily work in Jira workflows but also match your business processes with automation rules listening to Jira's various events like field, issue, project, and system events.

With the release of Jira Workflow Toolbox 2.9.0, Automation Toolbox will become an integral part of Jira Workflow Toolbox because we decided you should not need two apps for one common goal: Building the best processes to support your teams.

While the name remains the same, you can go way beyond your Jira workflows.

New features

• Automation rules are now available within JWT in order to perform Actions based on Triggers

Improvements

• A Get started page was added to serve as a central hub for accessing all JWT-related functions
• An option to suppress the default Jira email subject prefix was added to the Send an email post function

Bug fixes

• Several bug fixes

See the full release notes here.

🆕 JWT now includes automation rules! 🆕

A year ago we released our app Automation Toolbox to not only enable you to automate your daily work in Jira workflows but also match your business processes with automation rules listening to Jira's various events like field, issue, project, and system events.

With the release of Jira Workflow Toolbox 2.9.0, Automation Toolbox will become an integral part of Jira Workflow Toolbox because we decided you should not need two apps for one common goal: Building the best processes to support your teams.

While the name remains the same, you can go way beyond your Jira workflows.

New features

• Automation rules are now available within JWT in order to perform Actions based on Triggers

Improvements

• A Get started page was added to serve as a central hub for accessing all JWT-related functions
• An option to suppress the default Jira email subject prefix was added to the Send an email post function

Bug fixes

• Several bug fixes

See the full release notes here.

New features

• Added RUN_AS_LANG as a new language parameter to the expression parser
• Added RUN_AS_LOCAL as a new time zone parameter to the expression parser

Bug fixes

• The Send an email post function did not include zip files attached during the transition
• The Assign to Project Role post function was always executed by the current user
• The Assign to Project Role post function didn't work properly when selecting Last user or Previous user in project role
• The timeInStatus function returned negative values if the initial status was changed in the workflow
• The Epic Link field could not be edited inline within the 3rd party app Structure by ALM Works
• Adding a Transition issue post function caused problems in case the status or transition selection was not changed

New features

• Added RUN_AS_LANG as a new language parameter to the expression parser
• Added RUN_AS_LOCAL as a new time zone parameter to the expression parser

Bug fixes

• The Send an email post function did not include zip files attached during the transition
• The Assign to Project Role post function was always executed by the current user
• The Assign to Project Role post function didn't work properly when selecting Last user or Previous user in project role
• The timeInStatus function returned negative values if the initial status was changed in the workflow
• The Epic Link field could not be edited inline within the 3rd party app Structure by ALM Works
• Adding a Transition issue post function caused problems in case the status or transition selection was not changed

New features

• Added support for Botron's Configuration Manager for Jira (see our documentation)
• Added support for Jira 8.6.x

Bug fixes

• The Fields required or changed validator did not work properly when using version fields after upgrading to JWT version 2.7.1
• Jira Service Desk approval emails did not work properly when using JWT-related post functions on the transition to the approval step

New features

• Added support for Botron's Configuration Manager for Jira (see our documentation)
• Added support for Jira 8.6.x

Bug fixes

• The Fields required or changed validator did not work properly when using version fields after upgrading to JWT version 2.7.1
• Jira Service Desk approval emails did not work properly when using JWT-related post functions on the transition to the approval step

Bug fixes

• The function dateTimeToString() generated an error
• All functions returning users now exclude inactive users
• Conditions based on JQL expressions did not work properly when a query included an ORDER BY clause
• Multi-level cascading select fields from Sourcesense (3rd party app) could not be set
• Red asterisk in the Fields required or changed validator was not shown for some fields
• Fields required or change validator did not work properly for fields including a comma in their names
• "Message to show at failed validation" in validators was not shown next to the specified field in the create transition
• Performance improvements for the timeInStatus() function
• Conditions Only users in a field/Except users in field evaluated against the changed issue instead of the original issue

Bug fixes

• The function dateTimeToString() generated an error
• All functions returning users now exclude inactive users
• Conditions based on JQL expressions did not work properly when a query included an ORDER BY clause
• Multi-level cascading select fields from Sourcesense (3rd party app) could not be set
• Red asterisk in the Fields required or changed validator was not shown for some fields
• Fields required or change validator did not work properly for fields including a comma in their names
• "Message to show at failed validation" in validators was not shown next to the specified field in the create transition
• Performance improvements for the timeInStatus() function
• Conditions Only users in a field/Except users in field evaluated against the changed issue instead of the original issue

New features

• The Field is/isn't initialized validator was renamed to Fields required or changed
• The Field is/isn't initialized condition was renamed to Fields required
• The Fields required or changed validator and the Fields required condition can now validate multiple fields
• The field/s configured as required/initialized in the Fields required or changed validator is/are marked with an asterisk (*) in the transition screen

Improvements

• An optional delayed execution is added to the Move issues post function
• In the Send mail post function all the inactive users and email addresses with an incorrect format are filtered out

Several bug fixes

See the full release notes here.

New features

• The Field is/isn't initialized validator was renamed to Fields required or changed
• The Field is/isn't initialized condition was renamed to Fields required
• The Fields required or changed validator and the Fields required condition can now validate multiple fields
• The field/s configured as required/initialized in the Fields required or changed validator is/are marked with an asterisk (*) in the transition screen

Improvements

• An optional delayed execution is added to the Move issues post function
• In the Send mail post function all the inactive users and email addresses with an incorrect format are filtered out

Several bug fixes

See the full release notes here.

Bug fixes

• Last comment's visibility restrictions did not return the Service Desk visibility of a transition comment
• Value type Standard did not work properly when setting fields in the Create issues post function
• Disabling and enabling the app could produce a "Service proxy has been destroyed" error

Bug fixes

• Last comment's visibility restrictions did not return the Service Desk visibility of a transition comment
• Value type Standard did not work properly when setting fields in the Create issues post function
• Disabling and enabling the app could produce a "Service proxy has been destroyed" error

Bug fixes

• Setting Clear field value as value type in distinct post functions did not work properly for version and component fields
• Post functions stopped executing when trying to access a non-existent (e.g. deleted) custom field
• Executing Jira Workflow Toolbox post functions via the Workflow Enhancer for Jira app did not work properly

Bug fixes

• Setting Clear field value as value type in distinct post functions did not work properly for version and component fields
• Post functions stopped executing when trying to access a non-existent (e.g. deleted) custom field
• Executing Jira Workflow Toolbox post functions via the Workflow Enhancer for Jira app did not work properly

New expressions in the parser

• Several functions now support storing variables within an expression
• Added support for searching and obtaining historic values
• Functions to return the calendar week and day of the year
• Functions to return the time duration a field obtained a certain value
• Functions to return project versions ordered by their internal sequence

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

Several bug fixes

See the full release notes here.

New expressions in the parser

• Several functions now support storing variables within an expression
• Added support for searching and obtaining historic values
• Functions to return the calendar week and day of the year
• Functions to return the time duration a field obtained a certain value
• Functions to return project versions ordered by their internal sequence

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

Several bug fixes

See the full release notes here.

Bug fixes

• While performing the Move issues post function all the custom field values of the moved issue were deleted

Bug fixes

• While performing the Move issues post function all the custom field values of the moved issue were deleted

Bug fixes

• Create issues and subtasks post function bug when the option inherit rest of the fields was selected

Bug fixes

• Create issues and subtasks post function bug when the option inherit rest of the fields was selected

Improvements

• Added support to set the Portfolio Parent Link custom field by using an issue key
• Added Issue Security Scheme name to the Issue Security Level picker

Bug fixes

• Several bug fixes

See the full release notes here.

Improvements

• Added support to set the Portfolio Parent Link custom field by using an issue key
• Added Issue Security Scheme name to the Issue Security Level picker

Bug fixes

• Several bug fixes

See the full release notes here.

Improvements

• Group picker performance improvement
• The position of a post function does no longer affect its functionality except delayed issue transitions

Bug fixes

• Several bug fixes

See the full release notes here.

Improvements

• Group picker performance improvement
• The position of a post function does no longer affect its functionality except delayed issue transitions

Bug fixes

• Several bug fixes

See the full release notes here.

New features

• Move issues on a transition using the Move issues post function
• Use advanced parsing mode for composing meaningful error messages in all validators
• Added the xApps Library to use our Expression Parser in several upcoming apps (Automation Toolbox for Jira being the first)

Improvements

• Reference standard objects like issue types, statuses or resolutions by ID, e.g. use status(1) instead of "Open"
• Use IDs for custom field options, e.g. use option(10001) instead of "Option A"
• Skip validations for issues being created by email
• Set the assignee to Automatic
• Mark all values in a multi-valued field as required in the A field is/isn't initialized or has/hasn't been modified validator
• Use Standard option for fields in the Create issues and sub-tasks post function
• Parse text for selecting transitions and statuses within the Transition issues post function

Bug fixes

• Several bug fixes

See the full release notes here.

New features

• Move issues on a transition using the Move issues post function
• Use advanced parsing mode for composing meaningful error messages in all validators
• Added the xApps Library to use our Expression Parser in several upcoming apps (Automation Toolbox for Jira being the first)

Improvements

• Reference standard objects like issue types, statuses or resolutions by ID, e.g. use status(1) instead of "Open"
• Use IDs for custom field options, e.g. use option(10001) instead of "Option A"
• Skip validations for issues being created by email
• Set the assignee to Automatic
• Mark all values in a multi-valued field as required in the A field is/isn't initialized or has/hasn't been modified validator
• Use Standard option for fields in the Create issues and sub-tasks post function
• Parse text for selecting transitions and statuses within the Transition issues post function

Bug fixes

• Several bug fixes

See the full release notes here.

Jira 8 Compatibility

Bug fixes

• Issue creation under an epic, triggered by the epic itself, produced a deadlock because of the epic's change history entry which could not be created.
• When converting from string to number, the exponent 10 got cut off. Bug resurfaced in version 2.4.10.
• Daylight Saving Time changes at 00:00 AM negatively impacted several time-related functions.

Bug fixes

• Issue creation under an epic, triggered by the epic itself, produced a deadlock because of the epic's change history entry which could not be created.
• When converting from string to number, the exponent 10 got cut off. Bug resurfaced in version 2.4.10.
• Daylight Saving Time changes at 00:00 AM negatively impacted several time-related functions.

Bug fixes

• Calculated fields had been removed from the index in version 2.4.9 to prevent problems related to functions that require the index while the index is unavailable. Now the calculated fields are only removed from the index if functions are being used that require the index. e.g the function issuesFromJQL()
• The isJwtTriggeredTransition() function did not respect the issue creation when triggered by Jira Workflow Toolbox itself
• Fix in Ephemeral fields to prevent a NullPointer exception caused by empty objects generated by the Expression Parser Test page

Bug fixes

• Calculated fields had been removed from the index in version 2.4.9 to prevent problems related to functions that require the index while the index is unavailable. Now the calculated fields are only removed from the index if functions are being used that require the index. e.g the function issuesFromJQL()
• The isJwtTriggeredTransition() function did not respect the issue creation when triggered by Jira Workflow Toolbox itself
• Fix in Ephemeral fields to prevent a NullPointer exception caused by empty objects generated by the Expression Parser Test page

New features

• Target issue selection in Log work post function
• Parser rendering language can now be changed, the default setting is the Jira indexing language.

New expressions in the parser

• attachmentUrls(), attachmentUrls(issue list issue_list), attachmentUrls(string list attachments_regexp), attachmentUrls(issue list issue_list, string list attachments_regexp) - all functions return URLs to the selected attachment

and bug fixes.

Read the complete release notes here

New features

• Target issue selection in Log work post function
• Parser rendering language can now be changed, the default setting is the Jira indexing language.

New expressions in the parser

• attachmentUrls(), attachmentUrls(issue list issue_list), attachmentUrls(string list attachments_regexp), attachmentUrls(issue list issue_list, string list attachments_regexp) - all functions return URLs to the selected attachment

and bug fixes.

Read the complete release notes here

This is the first Atlassian approved data center compatible version of Jira Workflow Toolbox.

Improvements

• Reading new Insight custom field objects now returns a combination of the name and the key of insight objects. Examples: Main Server (SFT-243), Test Environment (CRM-21)
• Writing the new insight custom fields has been improved: the name, the key or a combination of name and key of insight objects are now accepted when setting insight fields. Examples: "Main Server", "SFT-243" or "Main Server (SFT-243)" are the 3 valid ways of setting an Insight field with a same object.

Bug fixes

• JWT calculated number and date-time fields returned error instead of null for issues not in the fields context
• Option Picker did not return Options with a corrupt database
• JWT now prevents creating issue links between an issue and itself
• Fixed several functions to work on the parser test page

Improvements

• Reading new Insight custom field objects now returns a combination of the name and the key of insight objects. Examples: Main Server (SFT-243), Test Environment (CRM-21)
• Writing the new insight custom fields has been improved: the name, the key or a combination of name and key of insight objects are now accepted when setting insight fields. Examples: "Main Server", "SFT-243" or "Main Server (SFT-243)" are the 3 valid ways of setting an Insight field with a same object.

Bug fixes

• JWT calculated number and date-time fields returned error instead of null for issues not in the fields context
• Option Picker did not return Options with a corrupt database
• JWT now prevents creating issue links between an issue and itself
• Fixed several functions to work on the parser test page

IMPROVEMENTS

• Improved support for new "Insight Object/s" custom field type.

BUG FIXES

• Numeric field code injectors don't show any the following field types: Date, Date-Time and Priority.
• Field code injectors in calculated fields are showing unwanted field codes associated to transition executions (eg. Transition's comment).
• We removed one of the examples of custom display format for Numeric Calculated Fields which was wrong.
• Cascading select comparer throws an error when an empty configuration of it is saved.
• Format field value post-function was interpreting the replacement string parameter as a regular expression instead of a string literal.
• Parameter replacement at parser functions replaceFirst(string, regex, replacement) and replaceAll(string, regex, replacement) was being interpreted as a regex instead of a string literal.

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

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.

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

Bugfix

• The "Send an E-Mail" post function does not work as expected after upgrading to version 2.4.1/2.4.2

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

Bugfixes

• 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.

New features

• Update issue fields (formerly known as Write fields on issues returned by JQL query or issue list)
  • target issue selection: Current Issue, Parent Issue, Linked Epic, and many more)
  • Simple selection of target field values: (Single Select, Multi Select, Components, ...)
  • Easily purge field values with the new "Clear field value" option

• Expression Parser Test page
  • test expressions against existing issues in real time
  • including syntax highlighting and syntax check

• Parser Functions
  • dateTimeToString(number t, string date_time_pattern , timeZone time_zone, language) : string
  • htmlToTxt(string s) : string
  • projectKeys() : string list
  • projectKeys(string category) : string list
  • projectName(string project_key) : string
  • projectCategory(string project_key) : string

Parametric issue type selection in post function "Create issues and sub-tasks"

IMPORTANT NOTE

In version 2.3.3 issues stopped to be immediately updated after each field writing. This modification of the historical behavior of JWT has caused problems in some workflows configured with previous versions of JWT. In this new version of JWT (2.3.4) we are adding a checkbox parameter for optionally updating the issue after a field writing.

IMPROVEMENTS

• Added optional parameter "Update issue immediately after field writing" to 12 post-functions. This parameter is checked in old post-function configurations.

BUG FIXES

• Unary minus operator caused NPE when applied on numeric expressions returning null.
• Optional parameter "Don't overwrite" wasn't working in post functions Read field from issues returned by JQL query or issue list and Read fields from linked issues or sub-tasks.
• Post function Send an email didn't manage correctly attachments using Cyrillic characters in the file name.
• Functions replaceFirst() and replaceAll() caused NPE when applied on null arguments.

New Features

• 8 new functions related with date-time calculations.

Improvements

• Maximum delay for delayed transition execution now is 60 s, instead of 30 s.

Bug Fixes

• Each field update done by JWT post-functions appeared in issue history separately.

• Issue #264 - Fixed bug with on functions datePart() and timePart() when used on the days where DST transition happens.

• Changed behavior of function addMonths() so that when adding 1 month to 30th April we will obtain 30th May instead of 31st May.

• Error in the way setting rules were rendered by "Syntax Check" button mainly on post-function "Set field as a function of other fields" and also on some other features.

• Parser functions that admits a comma separated list of usernames didn't filter duplicated values. In this version we implement a filter to avoid duplications.

• When using JWT post-functions for setting fields in "Create Issue" transition in JSD, emails were not being sent to approvers.Detailed release notes

Detailed Release Notes

Bug fixes

• Problem when setting field Epic Link on "Create issues and subtasks" post-function.
• Problem on "Assign to Project Role" post-function when using round-robin assignment on a queue containing only one user.
• Option for inheriting "Rest of field values" on "Create issues and subtasks" post-function is not working.
• When configuring option "Save issue keys..." on "Create issues and subtasks" post-function, it doesn't remain checked.

Improvements

• Online help links has been updated to new JWT's Documentation Site.

Bug fixes

• Issue #958 - Disabling options using Add or Disable option in Select List, Radio Button, Multi-Select List or Checkbox and Add or Disable option in Cascading Select post-functions where not working correctly.
• Virtual field "Target status" was returning step name instead of status name.
• Null Pointer Exception while evaluating certain boolean expressions.
• Null Pointer Exception when parameter n_days in null when invoking function addDaysSkippingWeekends(time, n_days, timezone).
• Bug Fix in Send an email post function when a recipient has no mail address

Detailed release notes

New Features

• Added new post-function Transition issues

• New parser functions: epic(), issuesUnderEpic(), siblingIssuesUnderEpic(), startDates(string versions), earliestUnreleasedUnarchivedVersion(),latestReleasedUnarchivedVersion() and more

Improvements

• Added new parameters to post-function Create issues and subtasks for optionally inheriting comments, attachments and issue links.

• Added new parameter Starting Date-Time to post-function Log Work.

See the full release notes under : https://apps.decadis.net/x/E4gb

Fixed a bug introduced in version 2.2.46 that affects only when we have a JWT post-function in transition "Create Issue" for setting fields, and we are creating issues using an email listener.

Detailed release notes

Detailed release notes

• Compatibility with JIRA 7.6.0
• Bug fix: Issue #885

This version fixes a problem affecting "Send an email" post-function.

Detailed release notes

Detailed release notes

Detailed release notes

Detailed release notes

Added 2 new read-only virtual fields:

• Sprint Start Date
• Sprint End Date

Added 2 new functions related with Custom Schedules.

Detailed release notes

Version 2.2.39 of JWT provides a highlight new feature: Support for Custom Schedules.

Now, you will be able to define complex schedules using a simple but incredibly powerful language (Schedule Definition Grammar).

Then you have a comprehensive set of new parser function to do any time calculation you might need on the schedules you have previously defined.

Example: do time calculations taking into account only time from 9:00 to 15:00 and 16:00 to 19:00 Mondays to Thursdays, and Fridays only from 9:00 to 15:00. You can also include common and personal holidays. Special schedules for the summer, or particular periods of the year, etc.

Believe me, there are no limits at schedules definition using SDG.

Detailed release notes.

Detailed release notes

Support for setting JSD "Organizations" custom field.

Other improvement and bug fix.

Detailed release notes

Added support for reading/setting multiple fields to the following 4 post-functions:

• Write field on linked issues or subtasks
• Read fields from linked issues or subtask
• Write field on issues returned by JQL Query or Issue List
• Read field from issues returned by JQL Query or Issue List

Detailed release notes

Detailed release notes

Detailed release notes

Detailed release notes

Detailed release notes

This version provides parameters for customizing the way Calculated Number Fields and Calculated Date-Time Fields are displayed.

Detailed release notes

Detailed release notes

This version provides for first time custom fields in Jira Workflow Toolbox:

• Calculated Text Field
• Calculated Number Field
• Calculated Date-Time Field

On the other hand this version provides several improvements and bug fixes.

Detailed release notes

Detailed release notes

• Fixed bug on 'Create issues and subtasks' post-function. Affects versions of Jira from 6.4 to 7.1.10.
• Support for custom fields provided by 'Dynamic Forms' add-on.

Detailed release notes

Detailed release notes

Fixed bug in parameter for Project selection in "Create issues and subtasks" post-function.

Detailed release notes

New Features:

• Added new "Create issues and subtasks" post-function:

Allows you to automatically create one or multiple new issues and subtasks when executing a transition in your workflows. You can also set the fields of the new issues based on the values of fields in other issues, and link the new issues to the other issues in your Jira instance.

Detailed release notes

BUGS FIXED:

• Version 2.2.22 introduced a bug affecting "Send an email" post-function when trying to send messages with attachments.
• Issue #431 - "Condition based on JQL query" takes too long to be evaluated when configured with a JQL query that returns a very big number of issues.

Detailed release notes

Among other improvements, a "Syntax Check" button has been added in all the features of the plugin, enabling to check on the fly the following:

• boolean expressions
• advanced parsing mode texts
• math/time calculations
• setting rules
• JQL queries.

Detailed release notes

BUG FIX: Syntax highlighting stopped working in version 2.2.20 for advanced parsing mode and math/time expressions.

This version fixes a bug that made the plugin fail with Internet Explorer.

Datailed release notes

HOT FIX

The following features are affected by a bug introduced in version 2.2.16:

• Condition based on JQL query
• Validation based on JQL query
• Write field on issues returned by JQL query
• Read field from issues returned by JQL query

It's highly recommended to update to 2.2.19 in case you are in versions 2.2.16, 2.2.17 or 2.2.18.

Detailed release notes

Detailed release notes

Version 2.2.16 introduced a bug affecting issue reindexation when issues are updated by a Jira Workflow Toolbox post-function in Jira 7.1.x.

Detailed release notes

Detailed release notes

Detailed release notes

Detailed release notes

Detailed release notes

This version includes a CRITICAL FIX for Jira 7.x. It's highly recommended to update if you are using Jira 7.x.

Detailed release notes

This version provides:

• A new post-function: Create an Email
• Support for conditional execution in most post-functions of the plugin.

Detailed release notes

Detailed release notes

Detailed release notes

Fixed UI bugs introduced by version 2.2.5.

HOTFIX: This version fixes a bug on "Read fields from linked issues or subtask" and "Read field from issues returned by JQL query" post-functions, that was introduced in version 2.2.2.

It's highly recommended to update, if you currently are using versions 2.2.2 or 2.2.3.

Detailed release notes

Detailed release notes

Detailed release notes

Detailed release notes

This version is released for fixing a quite important bug for users that are still using Jira with versions 5.0 to 6.2.2.

Bug Fixes

• Issue #178: Parent issue not being reindexed after being updated after having written a "Parent's..." virtual field.

First version compatible with Jira 7.

Added support for setting internal / public Jira Service Desk's comment visibility.

Detailed release notes.

Bug fixes

• Condition and Validator Users in a field are/aren't in a project role throw an exception when used with a "Multi User Picker" custom field that is uninitialized. This bug was introduced in version 2.1.34.

HOT FIX: This version fixes a bug (#169) on virtual fields "Issue status (delayed writing)" and "Execute transition (delayed execution)".

The bug affects versions 2.1.33 and 2.1.34. It's HIGHLY RECOMMENDED TO UPDATE from these versions to version 2.1.35.

Detailed release notes

Detailed release notes.

Detailed release notes

Detailed release notes

Detailed release notes.

Detailed release notes

Detailed release notes

Version 2.1.27 introduced a bug that prevented new configurations or editing current configurations in post-functions:

• "Read fields from linked issues or subtasks"
• "Write field on linked issues or subtasks" post-functions.

More details on fixed bug

Detailed release notes

Detailed release notes

Detailed release notes

Detailed release notes

Detailed release notes

Detailed release notes

Detailed release notes

Detailed release notes

NEW:

• Functions for advanced parsing mode in post-function "Copy parsed text to a field":

- dateToString(number t, time_zone, language)

- dateTimeToString(number t, time_zone, language)

- monthToString(number t, time_zone, language)

- dayOfTheWeekToString(number t, time_zone, language)

• Functions for boolean condition and validator:

- isInGroup(user, group)

- isInRole(user, projectRole, projectKey)

- isActive(user)

• New writable virtual field: "New watcher"

IMPROVEMENTS:

• Fields in some select list have been reordered.
• Post-function "Add or remove watchers" now supports also project roles.
• UI improvements

FIXED:

• Bugs in automatic conversion from "Basic" to "Advanced" parsing mode in "Copy parsed text to a field" post-function.
• Writing a "User" field into a "Multi User" field didn't work.
• Field "Parent's watchers" was failling.
• Post-function "Set field as a function of other fields" was not working correctly when a type 2 setting rule had field string values references: %{nnnnn}

NEW

• Added "advanced mode" to post-function "Copy parsed text to a field".

IMPROVEMENTS

• Expression parser now supports auto-casting from number types to strings.
• Field code injectors new insert field codes at cursor position.
• Added links to documentation.
• Other interface improvements.

FIXED

• Issue #47: Post-function "Create issue link" couldn't be configured since version 2.1.16.
• Issue #45
• Issue #41
• Post-function "Read fields from linked issues or subtasks" was failing when reading a Date or Date-Time field and the selected target was of type Number.
• Parser operator '+' for string values concatenation wasn't working correctly when left-hand side of the operator had a function call.

New

• Added function "matches" to expression parser allowing to check for regular expression matching.
• Added function "length" to expression parser allowing to get the number of characters of a string value.
• Levels in cascading select fields can be referenced using fields codes with format %{nnnnn.i} in "Boolean condition with math, date-time or text-string terms" and "Boolean validator with math, date-time or text-string terms".
• New virtual field "Number of transition attachments" allows to validate the number of attachments uploaded in a transition screen.
• New virtual field "Transition's comment" allows to validate the comment introduced in a transition screen.

Fixed:

• Virtual field "Number or attachments" didn't consider those attachments uploaded from transition screen.
• Issue #44 introduced in version 2.1.16 affecting post-function "Read project property".

New:

• New field "Watchers" to copy watchers between issues. Example
• Math-Time parser macros for days of the week and months.
• Support in "Set a field as a function of other fields" for setting field "Priority" using math expression. Example
• "Set a field from a set of rules based on regular expressions" has been renamed to "Set a field as a function of other fields". UI Improved UI and support for a new and more powerful kind of setting rule.
• "Condition based on mathematical or date-time expression" and "Validation based on mathematical or date-time expression" have been renamed to "Boolean condition with math, date-time or text-string terms" and "Boolean validator with math, date-time or text-string terms". Support for text-string terms. Improved UI.

Fixed:

• Texts with a valid date string value couldn't failed to set a Date-Time field.
• Bug when writing on custom fields in certain rare situations.
• Issue #39
• Issue #36
• Issue #40

New features:

• Post-function "Create issue link" now includes support for JQL queries: you can create issue links with issues returned by a JQL query.
• Improvements in mathematical and time expression calculator:
  • New function "getNumberOfAvailableItems( )"
  • Function "isNull()" now support "Select" and "Multi-Select" type of fields, in order to allow to be used in expressions including functions "numberOfSelectedItems({nnnnn})" and "numberOfAvailableItems( )".

Fixed bugs:

• "Condition on subtasks" and "Validation on subtasks" were not working correctly in certain circumstances when any of the following checkboxes were enabled: "Allow unselected issue types", "Allow unselected statuses" and "Allow unselected resolutions".

NEW FEATURES:

• Post-functions "Write field on linked issues or subtasks" and "Write field on linked issues or subtasks" now includes a parameter for reading or writing on sister subtasks, i.e., subtasks sharing the same parent. This parameter only makes sense when current issue is itself a subtask.
• Added new virtual fields "Parent's ephemeral number" and "Parent's ephemeral string". This fields are useful to exchange information among sister subtasks. For example, you can use them to implement semaphores to limit the number of issues to be transitioned by writing of virtual field "Issue status" or "Issue status (delayed writing)".
• Added mathematical functions "addMonths(date, n, timezone)" and "addYears(date, n, timezone)" for adding or subtracting whole months or years to date fields.

FEATURE IMPROVEMENTS:

• Revised text and messages to make clearer the usage of "Condition on linked issues", "Validation on linked issues", "Condition on subtasks" and "Validation on subtasks".

FIXED BUGS:

• Post-functions "Read fields from linked issues or subtasks" and "Write field on linked issues or subtasks" was writing or reading more than once the same subtask, when linked to current issue with selected issue link types.
• Issue #14: Post-function "Assigned by project role" was throwing a exception whenever the user to be assigned had been deleted.

FIXED BUGS

• "Break issue link" post-function not working properly.
• Ephemeral fields being cleared before transition ending, when transition screen contained field "Log Work" and a value was entered in that field.

NEW FEATURES

• Now you can include in your workflows dependencies to linked issue's or subtasks' "Resolution" value, thanks to new parameters added to "Condition on linked issues", "Validation on linked issues", "Condition on subtasks" and "Validation on subtasks".
  
• Operators "+" and "-" can be applied to virtual field "Labels" in order to add or remove labels from issues. For example, you can use "Copy parsed text to a field" or "Write field on linked issues or subtasks" post-functions to write into virtual field "Labels" strings like "+ label_1 label_2 label_3" and "- label_1" for adding 3 new labels and for removing 1 existing label respectively.
  

FIXED BUGS

• When reading a non-initialized cascading select custom an exception was thrown, making transition execution fail. In this new version of the plugin, in that cases an empty string is read and transition is completed successfully.
  

FIXED BUGS

• Custom fields of type "Group Picker" were not being correctly assigned, when selected as target field in post-functions.
  
• "Condition on subtasks" and "Validation on subtasks" were never satisfied when executed by subtasks, obviously since this kind of issues can't also have subtasks. Now, when executed by a subtask, this condition and validator are always satisfied.
• Version 2.1.4 of Jira Workflow Toolbox introduced a subtle change in behavior of "Issue status" and "Issue status (delayed writing)" virtual fields, making them not working when being written by post-function "Copy parsed text to a field".

FEATURE IMPROVEMENTS:

- This version supports Greenhopper's "Epic Links" in post-functions "Write field on linked issues or subtasks" and "Read fields from linked issues or subtasks", condition "Condition on linked issues" and validator "Validation on linked issues"

- Post-function "Create issue link" now can create more than one issue link at the same time. Parameter "Field containing the issues to be linked" now can receive a list of blank or comma separated issue keys for the issues to be linked. Also behaviour of the post-function has been changed to avoid throwing an exception if parameter "Field containing the issues to be linked" is left uninitialized.

FIXED BUGS:

- Virtual field "Parent's issue status (delayed writing)" wasn't working properly.

NEW FEATURES:

• New condtion "Condition on subtasks": condition based on number of subtasks, its issue type and status.
• New validator "Validation on subtasks": validation based on number of subtasks, its issue type and status.
• New post-function "Assign to Project Role": allows you to define a default user for a project role and set the issue to that user, or last assigned user playing a selected role.

IMPROVEMENTS:

* Warning message included in modules "Condition on linked issues", "Validation on linked issues" and "Write field on linked issues or subtasks" to indicate invalid configuration.

FIXED BUGS

• When copying "Multi User Picker" fields into fields of type Text or similar (Summary, Description, Unlimited Text, etc), no value was being copied.

First version of Jira Workflow Toolbox fully compatible with Jira 6.

FIXED BUGS

• Issue #10

COMPATIBILITY WITH Jira 6

This version of the plugin was initially released as compatible with Jira 6.0, but after detection of an issue (#10) concerning custom fields of type User Picker and Multi User Picker, it has been decided to remove that declaration of compatibility.

In this moment we are working to resolve this problem, in order to release as soon as possible a new version of the plugin fully compatible with Jira 6.

IMPORTANT WARNING

• Deprecated validator and condition "A field doesn't match a regular expression" has been removed from this version. If you were still using one of these deprecated features, you should replace them in your workflow with "Condition based on regular expression" or "Validation based on regular expression", before upgrading to this new version of the plugin.
  

NEW FEATURES

• New post-function "Log work". This new feature allows you to log work time, by inserting a new entry into issue's worklog, and update remaining estimate. Usage example.
  
• New parameter "Read also current issue" has been added to post-function "Read fields from linked issues or subtasks". With it you can include also current value of the issue in a math calculus (max, min, avg, etc) or you can get linked or subtasks values added to issue's current value.
  

FEATURE IMPROVEMENTS

• More field types are now available for parameter target field in post-function "Read a project property".
  
• Improved log output when writing on virtual field "Issue status" or "Issue status (delayed writing)". Now, you will be able to find out which transition is being triggered, when making issues progress through the workflow by means of writing on one of these virtual fields.
• Minor improvements in some configuration screens.

FIXED BUGS

• Condition based on mathematical or date-time expression was throwing an uncatched exception when one of the fields in the formula was initialized.
• Post-function "Set or create a project property" was modifying Project Lead and assigning it a nonexistent user.
• Virtual field "Parent's issue status (delayed writing)" wasn't available because of a bug.

NEW FEATURES

- Post-function "Read fields from linked issues or subtasks" now allows you to get the highest and lowest priority among linked issues or subtasks.

- Added an option to post-function "Read fields from linked issues or subtasks" for enabling recursive reading, i.e., you can read also transitively linked issues and subtasks. For example, this new feature allows you to get the highest priority among all directly or transitively blocking issues for a given issue.

- Added an option to post-function "Write field on linked issues or subtasks" for enabling recursive writing, i.e., you can read also transitively linked issues and subtasks. For example, this new feature enables you to make progress through the workflow any directly or transitively linked issue or subtasks when a blocking issue is resolved or closed.

IMPROVEMENTS

- Post-function "Read user property" now allows you to select as target field any type of field.

NEW FEATURES

• New writable virtual field called "Issue status (delayed writing)". The difference with virtual field "Issue status" is that writing into "Issue status (delayed writing)" is always done after transition has finished, while "Issue status" is written immediately. This delayed writing is very useful when the issues you want to make progress through the workflow (usually subtaks or linked issues) are blocked by status of current issue (using "Sub-Task Blocking Condition", "Condition on linked issues" or "Validation on linked issues").
  
• New function subtractDatesSkippingWeekends(minuend_date, subtrahend_date, time_zone) has been included in time expressions parser: is the equivalent of "minuend_date - subtrahend_date", with the difference that weekend periods are also subtracted from result, i.e., with this new function you can get the elapsed working time from subtrahend_date to minuend_date. This function may be very useful for SLA implementations in Jira.

IMPROVEMENTS

• Parser of logical expressions now implements a shortcut in logical operator "OR", with the same behavior as operator "||" in languages like C and JAVA. Let's suppose you have a logical expression like "A or B or C". The parser first evaluates term A, in case it's true it stops evaluating the formula and passes the validation; otherwise it evaluates term B, with the same behavior as before, and so on.
  
• Date and Date-Time fields can be assigned strings with format "yyyy/MM/dd [hh:mm]". In previous versions of the plugin, the only format admitted was the one configured in property jira.date.time.picker.java.format (configured in General Configuration (Advanced)).

IMPROVEMENTS

• Support for more than 500 new timezones in time expression parser.
  
• Improved parse error handling in mathematical and time expression parser. Now you get accurate information on where are the errors in your mathematical and time expressions.

• Virtual field Last comment was showing an uncontrolled error when issue had no comment.
  
• Time expression parser wasn't working properly when jira server and logged user timezones were different.
  

New Features

• Writing string "unassigned" into virtual field "Assignee" will turn issue unassigned.

Bug Fixes

• Post-function "Read fields from linked issues or subtasks" didn't work correctly when selected target field was of type "Date" or "Date and Time".
• Issue #4: "Condition on linked issues" and "Validation on linked issues" wasn't working correctly when project condition was set to "any but current".
• Issue #5: Exception not handled in "Condition based on mathematical or date-time expression" when a field in expression wasn't set.

FEATURE IMPROVEMENTS

• Fields "Date and time of creation", "Date and time of last update" and "Due date" are now also available in "Create Issue" transition.
  
• New virtual field "Date and time of resolution".
  
• Improved information in math and logical expression parser when failing due to a field not initialized.

BUG FIXES

• Assignment to Multi User fields was failing when the value to be assigned was a comma separated list of user names with some trailing or consecutive commas. (This bug was introduced in version 2.0.20.)
  
• When doing a cast from string to date or to date-time system's timezone was always being used. This version of the plugin uses logged user's timezone.
  
• In Jira 5.2.6 the log was registering a problem with thread synchronization.
  
• Function "addDaysSkippingWeekends(t, n, time_zone)" introduced some error in calculus when t was in weekend time.
  

OTHER THINGS

• Some code refactorization.
• Enriched log output.
• Warning message introduced in version 2.0.20 into "Copy parsed text to a field" configuration screen, has been removed, since it has been found that this problem only happens when using non-production HSQLDB databases.

New feature:

• Added feature to add or remove single items or sets of items to multi-valued fields (Multi Select, Multi Checkbox, Multi User Picker, Multi Group Picker, Components, Affected versions, Fixed versions and Version picker). More details on this feature.

• Added feature to assign an issue to a user in a project role. In case there are more than one user with the project role, you can set a user as default for a project role. You can use this functionality with every post-function in the plugin that allows you to write on any field of type User or Multi User. More details on this feature.

• New read-only virtual field "Last comment". This field allows you to implement a validation on the text of the comment introduced in a transition screen.

Other things:

• Minor revisions of text in configuration screens.

• Added a warning message in post-function "Copy parsed text to a field" in relation to a known issue when selected target is a custom field and post-function is executed the first in the transition.

New features:

• New function "addDaysSkippingWeekends(t, n, time_zone)" is available in mathematical and date-time expressions parser. This function adds or subtracts n days to a date field or time expression t ignoring weekends, i.e., if t represents a date-time which coincides with a Friday, adding n = 1 will return a date-time value representing next Monday. You can use n < 0 to subtract days to t.

• Modules "Compare two mathematical expressions or two date-time expressions" and "Compare two mathematical expressions or two date-time expressions" has been replaced by much more powerful modules based on a full logical expression processor: "Condition based on mathematical or date-time expression" and "Validation based on mathematical or date-time expression". These new modules allow the evaluation of complex logical expressions, with any number of comparisons connected by logical operators OR, AND and NOT. 

Feature improvements:

• JQL function projectsWhereDateProperty(property, operator, value) now supports dates with time part. Valid format is yyyy/MM/dd [hh:mm] or yyyy-MM-dd [hh:mm].