Minor version update
Version history
CloudJira Cloud2023-02-22Minor version update 3.3.1Jira Data Center 8.17.0 - 9.8.12023-04-27Maintenance release Improvements
- Improved thread handling when the app is disabled or uninstalled
Bug fixes
- Some issue link types were missing in the related picker
- Expert view for the Update fields based on rules post function did not work properly in Safari
- CVE-2023-24998 vulnerability fixed
3.3.1Jira Server 8.17.0 - 9.8.12023-04-27Maintenance release Improvements
- Improved thread handling when the app is disabled or uninstalled
Bug fixes
- Some issue link types were missing in the related picker
- Expert view for the Update fields based on rules post function did not work properly in Safari
- CVE-2023-24998 vulnerability fixed
3.3.0Jira Data Center 8.16.0 - 9.8.12023-02-22Feature and improvement release New features
- Expert view is now available for the Update fields based on rules post function
- Issue view is now refreshed automatically when the Transition issue post function is used
- New parser functions are now available to read remote links from issues
- Email notifications can now be configured within the Create issue action
Improvements
- Configuration tables in post function views are more responsible now
- Calendars expressions now come with additional examples
Bug fixes
- Workflow and transition selection did not work properly in the Transition issue post function under certain circumstances
- Send email action did not work properly, when a user was selected as target person
- Components were not set, when moving an issue with the Move issue post function
and many more! Check out the full release notes!
3.3.0Jira Server 8.16.0 - 9.8.12023-02-22Feature and improvement release New features
- Expert view is now available for the Update fields based on rules post function
- Issue view is now refreshed automatically when the Transition issue post function is used
- New parser functions are now available to read remote links from issues
- Email notifications can now be configured within the Create issue action
Improvements
- Configuration tables in post function views are more responsible now
- Calendars expressions now come with additional examples
Bug fixes
- Workflow and transition selection did not work properly in the Transition issue post function under certain circumstances
- Send email action did not work properly, when a user was selected as target person
- Components were not set, when moving an issue with the Move issue post function
and many more! Check out the full release notes!
3.2.0Jira Data Center 8.14.0 - 9.6.02022-11-22Make Jira your control center - execute remote actions within your workflows Introducing the new Execute remote action post function.
No matter if you want to create a Jira project, create a Confluence space or page or even create a card in Trello – with the latest Jira Workflow Toolbox you can do all of this and more.
3.2.0Jira Server 8.14.0 - 9.6.02022-11-22Make Jira your control center - execute remote actions within your workflows Introducing the new Execute remote action post function.
No matter if you want to create a Jira project, create a Confluence space or page or even create a card in Trello – with the latest Jira Workflow Toolbox you can do all of this and more.
3.1.7Jira Data Center 8.13.0 - 9.4.62022-09-13Maintenance release Bug fixes
- Some labels were not displayed correctly
3.1.7Jira Server 8.13.0 - 9.4.62022-09-13Maintenance release Bug fixes
- Some labels were not displayed correctly
3.1.6Jira Data Center 8.10.0 - 9.2.12022-06-20Feature and maintenance release New features
- Introducing the new Reindex issue action to be used in automation rules
- Added support for Issue Picker custom fields by ScriptRunner
Bug fixes
- User-related JQL functions did not work properly when having more than 1.000 users
- Referencing seed issues did not work properly in the Create issue post function since JWT 3.1.4
- The issue selector in automation rules did not work properly under certain circumstances
- Minor bug fixes related to the usage of JWT calendars
- The Create issue post function did not work properly when expressions used for summary or description returned null
- The stringToDate() parser function used the system timezone instead of the Jira default timezone
- Minor bug fixes related to the Configuration Manger for Jira (CMJ) support
3.1.6Jira Server 8.10.0 - 9.2.12022-06-20Feature and maintenance release New features
- Introducing the new Reindex issue action to be used in automation rules
- Added support for Issue Picker custom fields by ScriptRunner
Bug fixes
- User-related JQL functions did not work properly when having more than 1.000 users
- Referencing seed issues did not work properly in the Create issue post function since JWT 3.1.4
- The issue selector in automation rules did not work properly under certain circumstances
- Minor bug fixes related to the usage of JWT calendars
- The Create issue post function did not work properly when expressions used for summary or description returned null
- The stringToDate() parser function used the system timezone instead of the Jira default timezone
- Minor bug fixes related to the Configuration Manger for Jira (CMJ) support
3.1.5Jira Data Center 8.9.0 - 8.22.62022-04-20Maintenance release Improvements
- Fixed several security issues including CVE-2022-0540 and CVE-2022-22965
3.1.5Jira Server 8.9.0 - 8.22.62022-04-20Maintenance release Improvements
- Fixed several security issues including CVE-2022-0540 and CVE-2022-22965
3.1.4Jira Data Center 8.8.0 - 8.22.62022-03-10Maintenance release Improvements
- Revised and extended performance settings
- Jira Workflow Toolbox is now compatible with Jira 8.22
3.1.4Jira Server 8.8.0 - 8.22.62022-03-10Maintenance release Improvements
- Revised and extended performance settings
- Jira Workflow Toolbox is now compatible with Jira 8.22
3.1.3Jira Data Center 8.7.0 - 8.21.12022-01-05Maintenance release Improvements
- Improved workflow error messages in various places
- Improved form validation when using seed values in the expression editor
Bug fixes
- The rendering language was not set to system default on app installation
- Using special characters in workflow names could break some JWT forms
- The custom number format of calculated number fields did not align to the user's locale
- Insight object/s custom fields could not be updated by object key (only by object name)
- Several UI bug fixes
3.1.3Jira Server 8.7.0 - 8.21.12022-01-05Maintenance release Improvements
- Improved workflow error messages in various places
- Improved form validation when using seed values in the expression editor
Bug fixes
- The rendering language was not set to system default on app installation
- Using special characters in workflow names could break some JWT forms
- The custom number format of calculated number fields did not align to the user's locale
- Insight object/s custom fields could not be updated by object key (only by object name)
- Several UI bug fixes
3.1.2Jira Data Center 8.6.0 - 8.21.12021-10-28Maintenance release Improvements
- Improved and extended version of the in-app handbook
- Improved form validation for several post functions and automation actions in order to prevent misconfiguration
- Improved support of seed values and field codes for several post functions
- Improved performance of the Assign to project role post function and isInRole() function for instances with a large user count
- Warning message added when executing a Transition issue post function with an empty string as transition name
Bug fixes
- Several bug fixes
See the full release notes here.
3.1.2Jira Server 8.6.0 - 8.21.12021-10-28Maintenance release Improvements
- Improved and extended version of the in-app handbook
- Improved form validation for several post functions and automation actions in order to prevent misconfiguration
- Improved support of seed values and field codes for several post functions
- Improved performance of the Assign to project role post function and isInRole() function for instances with a large user count
- Warning message added when executing a Transition issue post function with an empty string as transition name
Bug fixes
- Several bug fixes
See the full release notes here.
3.1.1Jira Data Center 8.6.0 - 8.20.222021-10-01Issue searching 2.0 - run powerful parser expressions to refine your JQL queries New features
- Introducing new JQL functions to improve issue search, e.g. usersWithRoleInProject(), usersWithProperty(), linkedTo() or issueSelection()
- Extended support for Advanced Roadmaps related fields paired with additional expression parser functions
Improvements
- Improved handling of the Customer Request Type field for several post functions
- Improved form validation for editing validators, conditions and post functions
- Improved usage of logging levels regarding the evaluation of calculated fields
- Introducing anonymized app metrics
Bug fixes
- Validation on linked issues was missing the Epic option
- Setting the security level did not work properly for subtasks created by the Create issue post function
- Setting a select list (multiple choices) with the value of a select list (single choice) did not work properly
- Certain parser expressions could lead to corrupted Configuration Manager snapshots
See the full release notes.
3.1.1Jira Server 8.6.0 - 8.20.222021-10-01Issue searching 2.0 - run powerful parser expressions to refine your JQL queries New features
- Introducing new JQL functions to improve issue search, e.g. usersWithRoleInProject(), usersWithProperty(), linkedTo() or issueSelection()
- Extended support for Advanced Roadmaps related fields paired with additional expression parser functions
Improvements
- Improved handling of the Customer Request Type field for several post functions
- Improved form validation for editing validators, conditions and post functions
- Improved usage of logging levels regarding the evaluation of calculated fields
- Introducing anonymized app metrics
Bug fixes
- Validation on linked issues was missing the Epic option
- Setting the security level did not work properly for subtasks created by the Create issue post function
- Setting a select list (multiple choices) with the value of a select list (single choice) did not work properly
- Certain parser expressions could lead to corrupted Configuration Manager snapshots
See the full release notes.
3.0.3Jira Data Center 8.1.0 - 8.19.12021-03-26Compatibility release Improvements
Jira Workflow Toolbox is now compatible with Jira 8.16
3.0.3Jira Server 8.1.0 - 8.19.12021-03-26Compatibility release Improvements
Jira Workflow Toolbox is now compatible with Jira 8.16
3.0.2Jira Data Center 8.1.0 - 8.15.12021-03-12Maintenance release Improvements
- Smart UI improvements for the Expression parser handbook and several configuration components
- The customer request type field of Jira Service Management can now be set by name
Bug fixes
- Components and users could not be loaded or selected correctly in the configuration view of some post functions
- The "Team" field of the 3rd party app Tempo Timesheets could no longer be set when using Tempo Timesheets from version 11.0 onwards
- Reading values of cascading selects using the Basic or JQL mode of the Expression parser always returned the parent and the child level as a value
- Previously configured rules within the Update field based on rules post function containing a text comparison ignoring the case could not be edited anymore
- Issue links configured in the "Create issue" post function were not encoded correctly
- Seed issue field codes could not be used in Copy fields from linked issues or subtasks post function
3.0.2Jira Server 8.1.0 - 8.15.12021-03-12Maintenance release Improvements
- Smart UI improvements for the Expression parser handbook and several configuration components
- The customer request type field of Jira Service Management can now be set by name
Bug fixes
- Components and users could not be loaded or selected correctly in the configuration view of some post functions
- The "Team" field of the 3rd party app Tempo Timesheets could no longer be set when using Tempo Timesheets from version 11.0 onwards
- Reading values of cascading selects using the Basic or JQL mode of the Expression parser always returned the parent and the child level as a value
- Previously configured rules within the Update field based on rules post function containing a text comparison ignoring the case could not be edited anymore
- Issue links configured in the "Create issue" post function were not encoded correctly
- Seed issue field codes could not be used in Copy fields from linked issues or subtasks post function
3.0.1Jira Data Center 8.0.0 - 8.15.12021-02-02Maintenance release New features
- New field code and parser function to return an issue's project type
- New parser function to return a user key
Improvements
- Extended performance and special character support for the Update field based on rules post function
- Better handling of small values within Calculated Number Fields with "Hide the field from the issue view if the value is zero" enabled
- Added a warning message when testing expressions containing transition based field codes like %{issue.transition.comment}
Bug fixes
- The datePart() function did not consider the timezone parameter
- The time zone constants LOCAL and SERVER_LOCAL used the system's timezone instead of JIRA's default timezone
- Field codes containing date values returned the configured date picker format instead of the default JQL format when used within a JQL function
- The current user field code returned the user key instead of the username
- and many more
Check out the full release notes!
3.0.1Jira Server 8.0.0 - 8.15.12021-02-02Maintenance release New features
- New field code and parser function to return an issue's project type
- New parser function to return a user key
Improvements
- Extended performance and special character support for the Update field based on rules post function
- Better handling of small values within Calculated Number Fields with "Hide the field from the issue view if the value is zero" enabled
- Added a warning message when testing expressions containing transition based field codes like %{issue.transition.comment}
Bug fixes
- The datePart() function did not consider the timezone parameter
- The time zone constants LOCAL and SERVER_LOCAL used the system's timezone instead of JIRA's default timezone
- Field codes containing date values returned the configured date picker format instead of the default JQL format when used within a JQL function
- The current user field code returned the user key instead of the username
- and many more
Check out the full release notes!
3.0.0Jira Data Center 8.0.0 - 8.14.12020-11-26Taking workflow configuration seriously - introducing a brand-new JWT experience The biggest interface change ever in the history of JWT! We have worked a lot to give you the experience you have been waiting for having left almost no place untouched.
- A completely new UI offering a heavily improved user experience (👋 Hello to new field codes!)
- A new editing experience from start to end extended by many new helpful functions to make building workflows easier for you
- A revised documentation for those seeking assistance extended by tons of new use cases for all needs
See the full release notes here.
3.0.0Jira Server 8.0.0 - 8.14.12020-11-26Taking workflow configuration seriously - introducing a brand-new JWT experience The biggest interface change ever in the history of JWT! We have worked a lot to give you the experience you have been waiting for having left almost no place untouched.
- A completely new UI offering a heavily improved user experience (👋 Hello to new field codes!)
- A new editing experience from start to end extended by many new helpful functions to make building workflows easier for you
- A revised documentation for those seeking assistance extended by tons of new use cases for all needs
See the full release notes here.
2.9.3Jira Data Center 7.13.0 - 8.14.12020-09-08Maintenance release 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
2.9.3Jira Server 7.13.0 - 8.14.12020-09-08Maintenance release 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
2.9.2Jira Data Center 7.11.0 - 8.11.12020-06-10Maintenance release Bug fix
- Expression parser fields were broken in 2.9.1 when editing some workflow functions
2.9.2Jira Server 7.11.0 - 8.11.12020-06-10Maintenance release Bug fix
- Expression parser fields were broken in 2.9.1 when editing some workflow functions
2.9.1Jira Data Center 7.11.0 - 8.9.12020-06-05Maintenance release 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
2.9.1Jira Server 7.11.0 - 8.9.12020-06-05Maintenance release 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
2.9.0Jira Data Center 7.10.0 - 8.9.12020-04-23New feature: Automation rules 🆕 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.
2.9.0Jira Server 7.10.0 - 8.9.12020-04-23New feature: Automation rules 🆕 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.
2.8.1Jira Data Center 7.9.0 - 8.8.12020-03-04Maintenance release 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
2.8.1Jira Server 7.9.0 - 8.8.12020-03-04Maintenance release 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
2.8.0Jira Data Center 7.6.0 - 8.7.12020-01-13New feature: Support for Botron's Configuration Manager for Jira 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
2.8.0Jira Server 7.6.0 - 8.7.12020-01-13New feature: Support for Botron's Configuration Manager for Jira 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
2.7.1Jira Data Center 7.6.0 - 8.6.12019-11-21Maintenance release 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
2.7.1Jira Server 7.6.0 - 8.6.12019-11-21Maintenance release 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
2.7.0Jira Data Center 7.6.0 - 8.5.142019-10-17Make multiple fields required and mark them with a red asterisk 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.
2.7.0Jira Server 7.6.0 - 8.5.142019-10-17Make multiple fields required and mark them with a red asterisk 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.
2.6.2Jira Data Center 7.3.0 - 8.5.142019-08-16Maintenance release 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
2.6.2Jira Server 7.3.0 - 8.5.142019-08-16Maintenance release 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
2.6.1Jira Data Center 7.3.0 - 8.3.52019-07-25Maintenance release 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
2.6.1Jira Server 7.3.0 - 8.3.52019-07-25Maintenance release 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
2.6.0Jira Data Center 7.3.0 - 8.2.62019-07-15New functions in the parser and improvements 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.
2.6.0Jira Server 7.3.0 - 8.2.62019-07-15New functions in the parser and improvements 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.
2.5.4Jira Data Center 7.3.0 - 8.2.62019-06-06Maintenance release Bug fixes
- While performing the Move issues post function all the custom field values of the moved issue were deleted
2.5.4Jira Server 7.3.0 - 8.2.62019-06-06Maintenance release Bug fixes
- While performing the Move issues post function all the custom field values of the moved issue were deleted
2.5.3Jira Data Center 7.3.0 - 8.2.62019-05-27Maintenance release Bug fixes
- Create issues and subtasks post function bug when the option inherit rest of the fields was selected
2.5.3Jira Server 7.3.0 - 8.2.62019-05-27Maintenance release Bug fixes
- Create issues and subtasks post function bug when the option inherit rest of the fields was selected
2.5.2Jira Data Center 7.3.0 - 8.2.62019-05-22Maintenance release 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.
2.5.2Jira Server 7.3.0 - 8.2.62019-05-22Maintenance release 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.
2.5.1Jira Data Center 7.3.0 - 8.1.02019-05-20Maintenance release 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.
2.5.1Jira Server 7.3.0 - 8.1.32019-05-20Maintenance release 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.
2.5.0Jira Data Center 7.3.0 - 8.1.32019-04-08New feature: Move issues post function. And much more. 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.
2.5.0Jira Server 7.3.0 - 8.1.32019-04-08New feature: Move issues post function. And much more. 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.
2.4.12Jira Data Center 7.3.0 - 8.1.32019-02-12Jira 8 Compatibility Jira 8 Compatibility
2.4.12Jira Server 7.3.0 - 8.1.32019-02-12Jira 8 Compatibility No release notes.2.4.11Jira Data Center 6.3 - 7.13.182018-12-20Maintenance release 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.
2.4.11Jira Server 6.3 - 7.13.182018-12-20Maintenance release 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.
2.4.10Jira Data Center 6.3 - 7.13.182018-11-19Maintenance release 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
2.4.10Jira Server 6.3 - 7.13.182018-11-19Maintenance release 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
2.4.8Jira Data Center 6.3 - 7.12.32018-09-25New features, expressions, fixes. Last release compatible with Jira 6.3 - 7.2.15 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
2.4.8Jira Server 6.3 - 7.12.32018-09-25New features, expressions, fixes. Last release compatible with Jira 6.3 - 7.2.15 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
2.4.7Jira Data Center 6.3 - 7.11.22018-08-31Approved Data Center compatibility 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
2.4.7Jira Server 6.3 - 7.12.32018-08-31Improvements & Bug fixes 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
2.4.6Jira Server 6.3 - 7.12.32018-07-25Support for new Insight Object custom field types and Bug fixes 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.
2.4.5Jira Server 6.3 - 7.11.22018-06-29Maintenance release 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
2.4.4Jira Server 6.3 - 7.10.22018-06-21New parser function timeInStatus() and minor bugfixes 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
2.4.3Jira Server 6.3 - 7.10.22018-06-13Maintenance release Bugfix
- The "Send an E-Mail" post function does not work as expected after upgrading to version 2.4.1/2.4.2
2.4.2Jira Server 6.3 - 7.10.22018-06-11New features and UI performance improvements (replaces version 2.4.1) 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.
2.4.0Jira Server 6.3 - 7.10.22018-05-08New Update issue fields post function & expression parser test page 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"
- New parameter "timezone" added to Display Format configuration of Calculated Date-Time fields.
- Update issue fields (formerly known as Write fields on issues returned by JQL query or issue list)
2.3.4Jira Server 6.3 - 7.9.22018-04-05Maintenance release 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.
2.3.3Jira Server 6.3 - 7.8.42018-03-20New Parser functions related with date-time calculations and Bug Fixes 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
2.3.2Jira Server 6.3 - 7.8.42018-02-21Maintenance release 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.
2.3.1Jira Server 6.3 - 7.7.42018-02-09Bug fixes and Online Help links update 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
2.3.0Jira Server 6.3 - 7.7.42018-01-31Added new post-function "Transition issues" and more new features 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
2.2.47Jira Server 6.2.3 - 7.7.42018-01-02Maintenance release 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.
2.2.46Jira Server 6.2.3 - 7.6.172017-12-21Mixed Parsing Mode for "Send an Email" post-function. Bug fixes. 2.2.45Jira Server 6.2.3 - 7.6.172017-11-17Compatibility with JIRA 7.6.0 and Bug fix - Compatibility with JIRA 7.6.0
- Bug fix: Issue #885
2.2.44Jira Server 6.2.3 - 7.5.42017-11-07Maintenance release This version fixes a problem affecting "Send an email" post-function.
2.2.43Jira Server 6.2.3 - 7.5.42017-10-25Maintenance release 2.2.42Jira Server 6.2.3 - 7.5.42017-09-04Maintenance release 2.2.41Jira Server 6.2.3 - 7.4.62017-08-21Maintenance release 2.2.40Jira Server 6.2.3 - 7.4.62017-08-01New fields "Sprint Start Date" and "Sprint End Date". New schedule functions. Added 2 new read-only virtual fields:
- Sprint Start Date
- Sprint End Date
Added 2 new functions related with Custom Schedules.
2.2.39Jira Server 6.2.3 - 7.4.62017-07-05Support for Time Calculations using Custom Schedules 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.
2.2.38Jira Server 6.2.3 - 7.4.62017-06-15Improvements and bug fixes 2.2.37Jira Server 6.2.3 - 7.3.92017-05-27Support for JSD's Organizations. Bug fix on multi-field setting post-functions Support for setting JSD "Organizations" custom field.
Other improvement and bug fix.
2.2.36Jira Server 6.2.3 - 7.3.92017-04-21Multi field support for 4 post-functions. Bug fixes. Added support for reading/setting multiple fields to the following 4 post-functions:
2.2.35Jira Server 6.2.3 - 7.3.92017-03-23Improvements and bug fixes 2.2.34Jira Server 6.2.3 - 7.3.92017-03-15Improvements and bug fixes 2.2.33Jira Server 6.2.3 - 7.3.92017-03-08Support for round-robin assignment, and improved least busy user assignment 2.2.32Jira Server 6.2.3 - 7.3.92017-02-26New function "wikiToHTML()" and fixed bug on Calculated Text Field 2.2.31Jira Server 6.2.3 - 7.3.92017-02-14Improvements on Calculated Fields and Bug fixes. This version provides parameters for customizing the way Calculated Number Fields and Calculated Date-Time Fields are displayed.
2.2.30Jira Server 6.2.3 - 7.3.92017-02-03Bug fixes and 10 new functions for the parser 2.2.29Jira Server 6.2.3 - 7.3.92017-01-27New: 3 Calculated Custom Fields. Several improvements and bug fixes This version provides for first time custom fields in Jira Workflow Toolbox:
On the other hand this version provides several improvements and bug fixes.
2.2.28Jira Server 6.2.3 - 7.3.92016-12-15Bug fixes and some improvements 2.2.27Jira Server 6.2.3 - 7.2.152016-12-01Fixed bug on 'Create issues and subtasks'. 'Dynamic Forms' fields are supported. - 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.
2.2.26Jira Server 6.2.3 - 7.2.152016-11-252 New Virtual Fields, some important Improvements and Bug Fixes 2.2.25Jira Server 6.2.3 - 7.2.152016-11-15Bug fixes and improvements Fixed bug in parameter for Project selection in "Create issues and subtasks" post-function.
2.2.24Jira Server 6.2.3 - 7.2.152016-11-13New post-function "Create Issues and Subtasks" 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.
2.2.23Jira Server 6.2.3 - 7.2.152016-11-02Fixing bug in "Send an email" post-function when sending emails with attachments 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.
2.2.22Jira Server 6.2.3 - 7.2.152016-10-21"Syntax Check" feature for checking Expressions and JQL on the fly 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.
2.2.21Jira Server 6.2.3 - 7.2.152016-09-26Fixed bug: Syntax highlighting stopped working in version 2.2.20 BUG FIX: Syntax highlighting stopped working in version 2.2.20 for advanced parsing mode and math/time expressions.
2.2.20Jira Server 6.2.3 - 7.2.152016-09-23Support for Internet Explorer. Other bug fixes and improvements. This version fixes a bug that made the plugin fail with Internet Explorer.
2.2.19Jira Server 6.2.3 - 7.2.152016-09-08HOT FIX on JQL based features & Improvement on "Send an email" post-function 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.
2.2.18Jira Server 6.2.3 - 7.2.152016-08-30Support for "Insight - Asset Management" custom fields and Bug fixes 2.2.17Jira Server 6.2.3 - 7.2.152016-08-23HOT FIX on a bug introduced in version 2.2.16 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.
2.2.15Jira Server 6.2.3 - 7.1.102016-08-05Improvements and bug fixes 2.2.14Jira Server 6.2.3 - 7.1.102016-07-17Bug fixes 2.2.13Jira Server 6.2.3 - 7.1.102016-06-29Bug fixes 2.2.12Jira Server 6.2.3 - 7.1.102016-06-20Improvements and bug fixes 2.2.11Jira Server 6.2.3 - 7.1.102016-05-06Some improvements and bug fixes 2.2.10Jira Server 6.2.3 - 7.1.102016-04-26Bug fixes (critical fix for Jira 7.x). Important parser performance improvement. This version includes a CRITICAL FIX for Jira 7.x. It's highly recommended to update if you are using Jira 7.x.
2.2.9Jira Server 6.2.3 - 7.1.102016-03-23New post-function "Send an email". Added Conditional Execution to post-functions This version provides:
- A new post-function: Create an Email
- Support for conditional execution in most post-functions of the plugin.
2.2.8Jira Server 6.2.3 - 7.1.102016-02-25Important bug fixes, parser improvements and new functions 2.2.7Jira Server 6.2.3 - 7.1.102016-02-01New parser functions and bug fixes 2.2.6Jira Server 6.2.3 - 7.0.112016-01-15Fixed UI bugs Fixed UI bugs introduced by version 2.2.5.
2.2.5Jira Server 6.2.3 - 7.0.112016-01-13HOT FIX and UI Improvements 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.
2.2.3Jira Server 6.2.3 - 7.0.112015-12-22Bug fixes 2.2.2Jira Server 6.2.3 - 7.0.112015-12-14New Features, Improvements and Bug Fixes 2.2.1Jira Server 6.2.3 - 7.0.112015-10-28New features, improvements and bug fixes. 2.1.37Jira Server 5.0 - 6.2.22015-10-28Fixed bug 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.
2.2Jira Server 6.2.3 - 7.0.112015-10-07Compatibility with Jira 7. Support for JSD internal / public comment visibility. First version compatible with Jira 7.
Added support for setting internal / public Jira Service Desk's comment visibility.
2.1.36Jira Server 5.0 - 6.4.142015-09-10Bug fixed on " Users in a field are/aren't in a project role" cond and validat. 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.
2.1.35Jira Server 5.0 - 6.4.142015-09-08HOT FIX: Bug in delayed transition executions. Affected versions: 2.1.33, 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.
2.1.34Jira Server 5.0 - 6.4.142015-08-14New features, improvements and bug fixes. Last version compatible with Jira 5.x. 2.1.33Jira Server 5.0 - 6.4.142015-07-23New post-function "Parse field for extracting data" and much more. Bug fixes. 2.1.32Jira Server 5.0 - 6.4.142015-06-16New features, improvements and bug fixes 2.1.31Jira Server 5.0 - 6.4.142015-05-08New features, improvements and bug fixes. 2.1.30Jira Server 5.0 - 6.4.142015-03-29Several bug fixes and a new post-function 2.1.29Jira Server 5.0 - 6.4.142015-03-18Compatibility Jira 6.4, improved expression editor, other improvements. 2.1.28Jira Server 5.0 - 6.3.152015-02-25Hotfix - Bug in "Read/Write fields from/to linked issues or subtasks" 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.
2.1.27Jira Server 5.0 - 6.3.152015-02-21New features, improvements and bug fixes 2.1.26Jira Server 5.0 - 6.3.152015-02-06Several improvements and bug fixes 2.1.25Jira Server 5.0 - 6.3.152015-01-07Bug fixes and some improvements. New virtual field "Transition's attachments". 2.1.24Jira Server 5.0 - 6.3.152014-12-22Multi-language support in custom validation messages. Improvements and bug fixes 2.1.23Jira Server 5.0 - 6.3.152014-12-11New features (historic field values), improvements and bug fixes. 2.1.22Jira Server 5.0 - 6.3.152014-10-06Fixed bugs and many improvements and new features. 2.1.21Jira Server 5.0 - 6.3.152014-09-15New: 21 functions and 4 operators in parser. Several improvements and bug fixes. 2.1.20Jira Server 5.0 - 6.3.152014-08-1510 new virtual fields and 16 functions to add linked issues and subtasks 2.1.19Jira Server 5.0 - 6.3.152014-05-317 new functions in the parser and virtual field "New watcher". Fixed some bugs. 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}
2.1.18Jira Server 5.0 - 6.2.72014-05-22Advanced mode in "Copy parsed text to a field". Bugs fixed. 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.
2.1.17Jira Server 5.0 - 6.2.72014-05-12Fixed bug on "Read project property" introduced in version 2.1.16. 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".
2.1.16Jira Server 5.0 - 6.2.72014-05-06Major feature improvements and several bug fixes 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:
2.1.15Jira Server 5.0 - 6.2.72014-03-17JQL support in "Create issue link". Fix in "Condition/Validation on subtasks". 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".
2.1.14Jira Server 5.0 - 6.2.72014-02-23Feature improvements and bug fixes. New in this release
- New function "isNull({nnnnn})" for math/time parser.
- New fields "New comment" and "Parent's new comment" for inserting comments simply by writing a text into these fields.
- New field "Last comment's visibility" allows to set visibility of last comment simply by writing a Project Role name or Group name on it.
- Support for "Jira Misc Custom Fields" add-on
- New assignment modes in post-function "Assign to Project Role"
- random user in project role
- least busy user in project role
Fixed in this release
- Post-function "Assign to Project Role" wasn't excluding inactive users as assignable.
- Writing on "Parent's issue status (delayed writting)" wasn't working correctly.
- "Validator on linked issues" couldn't be used in "Create Issue" transition. Now you can use this feature to validate the links set in issue creation screen.
- Texts in configuration screens of "Condition on a list of issue keys" and "Validation on a list of issue keys" has been revised.
2.1.13Jira Server 5.0 - 6.1.92013-12-28Fixed bug in "Read field from issues returned by JQL query". New in this release
- Post-function "Add comment" now lets you limit visibility by group or by project role.
Fixed in this release
- Post-function "Read field from issues returned by JQL query" was not working ok when reading text fields.
- Some improvements in error messages returned by post-functions "Write field on linked issues or subtasks" and "Read field from issues returned by JQL query".
2.1.12Jira Server 5.0 - 6.1.92013-12-08Improved JQL features, support for Multi-Level Cascading. Bug fixes. New in this release
- Features "Condition based on JQL query", "Validation based on JQL query", "Read field from issues returned by JQL query" and "Write field on issues returned by JQL query" now support field values replacement, this way you can create dynamic JQL queries, with literals being replaced by field values at execution time.
- Added support for "Multi Level Cascading Select" custom fields, which now can be read and set. To read value of a level use %{nnnnn.i}, being i the level to be read.
Fixed in this release
- Conditions "Only user in custom field" and "Except user in custom field" were not working correctly when user name used capital letters.
- Virtual field "Current user's email" was returning an incorrect value.
2.1.11Jira Server 5.0 - 6.1.92013-11-19Fixed bug making 4 new modules in version 2.1.10 not working with Jira 5.x Fixed in this release
4 new modules introduced in version 2.1.10 were not working in Jira 5.x:
- Condition "Condition based on JQL query"
- Validator "Validation based on JQL query"
- Post-function "Read field from issues returned by JQL query"
- Post-function "Write field on issues returned by JQL query"
2.1.10Jira Server 5.0 - 6.1.92013-11-14New condition, validator and post-functions based on JQL queries. New in this release
- Condition "Condition based on JQL query"
- Validator "Validation based on JQL query"
- Post-function "Read field from issues returned by JQL query"
- Post-function "Write field on issues returned by JQL query"
- Virtual field "Components leaders" which returns the user names of leaders of selected components. It can be used to assign issue to leader of selected component.
Fixed in this release
- Virtual field "Parent's fixed versions" was not available
- Summary is cropped automatically when trying to write more than 255 characters.
2.1.8Jira Server 5.0 - 6.1.92013-09-15Write and read sister subtasks. New virtual fields. Bug fixes. 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.
2.1.7Jira Server 5.0 - 6.0.82013-08-18Fixed bugs: "Break link" post-function and ephemeral fields. 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.
FEATURE IMPROVEMENT- Improved warning information when configuring "Condition on linked issues", "Validation on linked issues", "Condition on subtasks" and "Validation on subtasks".
2.1.6Jira Server 5.0 - 6.0.82013-08-08New features: Add and remove labels from issue. Make your workflows dependent on linked issue's and subtasks' "Resolution" value. 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.
- 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".
2.1.5Jira Server 5.0 - 6.0.82013-07-20Issue fixes on "Condition on subtasks" and "Validation on subtasks", virtual fields "Issue status" and "Issue status (delayed writing)", and support for "Group Picker" custom fields. 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".
- Custom fields of type "Group Picker" were not being correctly assigned, when selected as target field in post-functions.
2.1.4Jira Server 5.0 - 6.0.82013-07-07Support for Greenhopper's "Epic Links". Improvements in post-function "Create issue link". Fixed bug in virtual field "Parent's issue status (delayed writing)". 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.
2.1.3Jira Server 5.0 - 6.0.82013-06-16Added 3 new features: "Condition on subtasks", "Validation on subtasks" and post-function "Assign to Project Role". 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.
2.1.2Jira Server 5.0 - 6.0.82013-06-06Fixed bug when copying "Multi User Picker" fields on text like fields. 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.
2.1.1Jira Server 5.0 - 6.0.82013-06-04First version fully compatible with Jira 6. 2.1Jira Server 5.0 - 5.2.112013-05-25New post-function "Log Work". Removed deprecated feature "A field doesn't match a regular expression". Feature improvements and bug fixes. 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.
- 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.