Fixed a bug where german umlauts were not correctly displayed when they are set in a error message for Validators

Fixed a bug where german umlauts were not correctly displayed when they are set in a error message for Validators

Fixed a bug where german umlauts were not correctly displayed when they are set in a error message for Validators

Fixed a bug where german umlauts were not correctly displayed when they are set in a error message for Validators

Jira 9 compatibility

Jira 9 compatibility

Fixed the Security Vulnerability Spring Framework (CVE-2022-22965) Update to Spring Framework 5.2.20& Bug fixes

Fixed the Security Vulnerability Spring Framework (CVE-2022-22965) Update to Spring Framework 5.2.20& Bug fixes

• We fixed a Bug where the combination of two post functions could lead to an error when creating a new Issue with our Create and Link post function.

• We fixed a Bug in our Required Fields Validator, where red asterisks didn't appear on Userpicker Custom Fields.
• We improved our Default Values feature by supporting Project Components.

• We improved our Default Values feature, where references to deleted custom fields and/or issue types are now automatically cleaned up.

• We fixed a bug where Version custom fields could not be selected in our "Copy Field Value" post function.

We now officially support Project Configurator for Jira to make migrations easier for you.

Please note that due to a limitation in the API it is currently not possible to support the Condition inside the Required Fields Validator. If you use this feature, please make sure to update references to custom fields in those functions manually. Once the API is ready, we'll update the compatibility.

Also, Default Values for Create Screens are currently not supported. Any references to custom fields have to be updated manually.

Please contact our support if you have any questions.

• We improved ourUpdate/Set Field to predefined value post function by supporting more system fields
• We improved our Update/Set Field to predefined value post function by adding the ability to configure date patterns
• We improved our Copy Field Value post function by adding the ability to run the function as a different (technical) user
• We improved our Set Security Level post function by adding the ability to run the function as a different (technical) user
• We fixed a bug in our Required Fields validator, where fields were not validated when the field was on a transition screen

We now officially support Configuration Manager for Jira to make migrations easier for you.

Please note that due to a limitation in the API it is currently not possible to support the Condition inside the Required Fields Validator. If you use this feature, please make sure to update references to custom fields in those functions manually. Once the API is ready, we'll update the compatibility.

Please contact our support if you have any questions.

• we fixed a bug in our "Transition Linked Issue" post function, where older configurations were broken due to missing legacy handling

• we improved our "User in Group" condition/validator to check for negated result
• we improved our "User in Project Role" condition/validator to check for negated results
• we improved our "Transition linked Issues" post function to copy fields during the transition

• We fixed a Bug where the combination of two post functions could lead to an error when creating a new Issue with our Create and Link post function.

• We fixed a Bug in our Required Fields Validator, where red asterisks didn't appear on Userpicker Custom Fields.
• We improved our Default Values feature by supporting Project Components.

• We improved our Default Values feature, where references to deleted custom fields and/or issue types are now automatically cleaned up.

• We fixed a bug where Version custom fields could not be selected in our "Copy Field Value" post function.

We now officially support Project Configurator for Jira to make migrations easier for you.

Please note that due to a limitation in the API it is currently not possible to support the Condition inside the Required Fields Validator. If you use this feature, please make sure to update references to custom fields in those functions manually. Once the API is ready, we'll update the compatibility.

Also, Default Values for Create Screens are currently not supported. Any references to custom fields have to be updated manually.

Please contact our support if you have any questions.

• We improved ourUpdate/Set Field to predefined value post function by supporting more system fields
• We improved our Update/Set Field to predefined value post function by adding the ability to configure date patterns
• We improved our Copy Field Value post function by adding the ability to run the function as a different (technical) user
• We improved our Set Security Level post function by adding the ability to run the function as a different (technical) user
• We fixed a bug in our Required Fields validator, where fields were not validated when the field was on a transition screen

We now officially support Configuration Manager for Jira to make migrations easier for you.

Please note that due to a limitation in the API it is currently not possible to support the Condition inside the Required Fields Validator. If you use this feature, please make sure to update references to custom fields in those functions manually. Once the API is ready, we'll update the compatibility.

Please contact our support if you have any questions.

• we fixed a bug in our "Transition Linked Issue" post function, where older configurations were broken due to missing legacy handling

• we improved our "User in Group" condition/validator to check for negated result
• we improved our "User in Project Role" condition/validator to check for negated results
• we improved our "Transition linked Issues" post function to copy fields during the transition

• We fixed a bug, where assigning an issue didn't work due to lacking user permission

• We fixed a bug, where setting the assignee during issue creation didn't work properly
• We improved our "Create a new linked Issue" post function to handle Portfolio hierarchies
• We improved our "Create a new linkes Issue" post function to create issues in several projects by supporting the selection in a Multi Picker custom field

• We fixed a bug, where the IN operator didn't work for multiple Resolutions in our Field Value condition/validator
• We fixed a bug in our "Update/Set Field to predefined value" post function, where Multi Group picker was not supported
• We fixed a bug, where the initial save of our "Create a new Linked Issue" post function was not working
• We added the "Created" system field as a source in our "Copy Field Value" post function

• We improved the error message in our Create and Link post function, to give the user a better explanation what went wrong, when a new issue can not be created
• We improved the validation handling inside workflow function configurations
• We improved the Copy Field Values post function, where now the CWX Issue Picker custom field is supported
• We fixed a Bug in our Required Fields validator, where Conditions couldn't be removed, once configured
• We fixed a Bug in our User in Project Role(s) condition and validator, where renaming a project role lead to an error
• We fixed a Bug in our Copy Field Value(s) between related Issues post function, where a configuration for a sub-task lead to an error when executed in a regular issue

• We added a new post function "Copy Field Value(s) between related Issues" that copies values between related issues on a transition. It supports Parent/Sub-task and Epic/Story relations in both directions.
• We set two post functions to deprecated (Copy Field Value From Sub-Task to Parent Issue & Copy Field Value From Parent Issue to Sub-Task) as they are both included in our new post function "Copy Field Value(s) between related Issues".
• We fixed a Bug, where sometimes configured default values stayed on the screen after switching to an issue type without a default value.
• We fixed a Bug, where values changed by our post functions could not be re-used in following post functions.
• We fixed a Bug, where options in "Copy Field Value" Post Function were empty

• We fixed a bug, where special characters in individual error messages where not unescaped when displayed to the user
• We fixed a bug in User In Field condition/validator, where single user custom fields did not work properly

• We fixed a Bug, where the Required Field Validator did not work correctly when the Scriptrunner App was installed
• We fixed a Bug, where some operators did not work in combination with single select and radio custom fields
• We fixed a Bug, where some WES functions could not be deleted after a configured custom field got deleted
• We fixed a Bug, where default values didn’t work on specific create screens

• New post function: "Clear Field Value(s)" to clear any field values on a transition
• Improvement of "User in Field" condition/validator: you can now choose from multiple fields and decide between "all", "none" or "at least in one" functions
• Improvement of the conditional feature inside the "Required Fields" validator: Conditions now get loaded with full JavaScript functionality
• We fixed a bug inside "Create a new Linked Issue" post function, where already saved issue types that are not available anymore, were not shown as errors to to the Admin
• We fixed a bug inside "Field Compare" condition/validator, where fields provided by other Apps could not be used

• We extended the "Required Fields" Validator with a conditional execution. Please try it out and let us know what you think. We might add this feature to other Validators and Post Functions.
• We changed some UI elements to integrate better with Jira's standard UI.
• We improved the existing "User in Field Condition/Validator" to check also for groups, configured in a custom field.
• We fixed a bug where the Resolution field didn't work as expected.

• We fixed a Bug, where the error message for the Copy Fields post-function was misleading
• We fixed a Bug in User in Group condition/validator, where group names including commas were not working correctly

• we fixed a bug, where fields with default values were not cleared after switching the issue type to one without default values (PBT-66)

• Compatibility to Jira 8.4.x
• We fixed a bug in Field Compare Validator/Condition, where multiple values for Option ID's were not possible to configure
• We fixed a bug in Required Fields Validator, where Tempo "Account" custom field was not treated as empty
• For better performance at startup we no longer check existing workflows for deprecated functions. Deprecated functions now always get disabled. Read more about deprecated functions in our documentation.
• Support for Scripted User custom field (by Misc Custom Fields App) in Assign to User specified in (Custom) Field Post Function
• Improved JQL Validator/Condition to handle nested queries

• support of user and multi-user fields in Field Compare Validator
• support of Misc Custom Field calculated user field in Field Compare Validator
• general support of original estimate and remaining estimate system fields in copy functions

• Support of "Secure Fields" User Custom Field types
• New operator "CONTAINS" for Field Compare Validator/Condition

• new Validator/Condition: validate the current issue against a JQL expression
• Bugfix: we fixed a Bug where "Time Spent" was not handled correctly in the Required Fields Validator

Data Center compatibility

• we fixed a bug in our "Transition Linked Issue" post function, where older configurations were broken due to missing legacy handling

• we improved our "User in Group" condition/validator to check for negated result
• we improved our "User in Project Role" condition/validator to check for negated results
• we improved our "Transition linked Issues" post function to copy fields during the transition

• We fixed a bug, where assigning an issue didn't work due to lacking user permission

• We fixed a bug, where setting the assignee during issue creation didn't work properly
• We improved our "Create a new linked Issue" post function to handle Portfolio hierarchies
• We improved our "Create a new linkes Issue" post function to create issues in several projects by supporting the selection in a Multi Picker custom field

• We fixed a bug, where the IN operator didn't work for multiple Resolutions in our Field Value condition/validator
• We fixed a bug in our "Update/Set Field to predefined value" post function, where Multi Group picker was not supported
• We fixed a bug, where the initial save of our "Create a new Linked Issue" post function was not working
• We added the "Created" system field as a source in our "Copy Field Value" post function

• We improved the error message in our Create and Link post function, to give the user a better explanation what went wrong , when a new issue can not be created
• We improved the validation handling inside workflow function configurations
• We improved the Copy Field Values post function, where now the CWX Issue Picker custom field is supported
• We fixed a Bug in our Required Fields validator, where Conditions couldn't be removed, once configured
• We fixed a Bug in our User in Project Role(s) condition and validator, where renaming a project role lead to an error
• We fixed a Bug in our Copy Field Value(s) between related Issues post function, where a configuration for a sub-task lead to an error when executed in a regular issue

• We added a new post function "Copy Field Value(s) between related Issues" that copies values between related issues on a transition. It supports Parent/Sub-task and Epic/Story relations in both directions.
• We set two post functions to deprecated (Copy Field Value From Sub-Task to Parent Issue & Copy Field Value From Parent Issue to Sub-Task) as they are both included in our new post function "Copy Field Value(s) between related Issues".
• We fixed a Bug, where sometimes configured default values stayed on the screen after switching to an issue type without a default value.
• We fixed a Bug, where values changed by our post functions could not be re-used in following post functions.
• We fixed a Bug, where options in "Copy Field Value" Post Function were empty

• We fixed a bug, where special characters in individual error messages where not unescaped when displayed to the user
• We fixed a bug in User In Field condition/validator, where single user custom fields did not work properly

• We fixed a Bug, where the Required Field Validator did not work correctly when the Scriptrunner App was installed
• We fixed a Bug, where some operators did not work in combination with single select and radio custom fields
• We fixed a Bug, where some WES functions could not be deleted after a configured custom field got deleted
• We fixed a Bug, where default values didn’t work on specific create screens

• New post function: "Clear Field Value(s)" to clear any field values on a transition
• Improvement of "User in Field" condition/validator: you can now choose from multiple fields and decide between "all", "none" or "at least in one" functions
• Improvement of the conditional feature inside the "Required Fields" validator: Conditions now get loaded with full JavaScript functionality
• We fixed a bug inside "Create a new Linked Issue" post function, where already saved issue types that are not available anymore, were not shown as errors to to the Admin
• We fixed a bug inside "Field Compare" condition/validator, where fields provided by other Apps could not be used

Happy New Year 2020!

We are thrilled to provided you with a new version of Workflow Essentials, including the following features:

• We extended the "Required Fields" Validator with a conditional execution. Please try it out and let us know what you think. We might add this feature to other Validators and Post Functions.
• We changed some UI elements to integrate better with Jira's standard UI.
• We improved the existing "User in Field Condition/Validator" to check also for groups, configured in a custom field.
• We fixed a bug where the Resolution field didn't work as expected.

• We fixed a Bug, where the error message for the Copy Fields post-function was misleading
• We fixed a Bug in User in Group condition/validator, where group names including commas were not working correctly

• we fixed a bug, where fields with default values were not cleared after switching the issue type to one without default values (PBT-66)

• We fixed a bug with Default Values, where values of rich-text editor fields where not set when placed on tabs
• We fixed a bug in Field Compare Validator/Condition, where multiple values for Option ID's were not possible to configure
• We fixed a bug in Required Fields Validator, where Tempo "Account" custom field was not treated as empty
• For better performance at startup we no longer check existing workflows for deprecated functions. Deprecated functions now always get disabled. Read more about deprecated functions in our documentation.
• Support for Scripted User custom field (by Misc Custom Fields App) in Assign to User specified in (Custom) Field Post Function
• Improved JQL Validator/Condition to handle nested queries

• support of user and multi-user fields in Field Compare Validator
• support of Misc Custom Field calculated user field in Field Compare Validator
• general support of original estimate and remaining estimate system fields in copy functions

• Support of "Secure Fields" User Custom Field types
• New operator "CONTAINS" for Field Compare Validator/Condition

• new Validator/Condition: validate the current issue against a JQL expression
• Bugfix: we fixed a Bug where "Time Spent" was not handled correctly in the Required Fields Validator

Data Center compatibility

• We fixed a bug, where assigning an issue didn't work due to lacking user permission

• We fixed a bug, where setting the assignee during issue creation didn't work properly
• We improved our "Create a new linked Issue" post function to handle Portfolio hierarchies
• We improved our "Create a new linkes Issue" post function to create issues in several projects by supporting the selection in a Multi Picker custom field

• We fixed a bug, where the IN operator didn't work for multiple Resolutions in our Field Value condition/validator
• We fixed a bug in our "Update/Set Field to predefined value" post function, where Multi Group picker was not supported
• We fixed a bug, where the initial save of our "Create a new Linked Issue" post function was not working
• We added the "Created" system field as a source in our "Copy Field Value" post function

• We improved the error message in our Create and Link post function, to give the user a better explanation what went wrong , when a new issue can not be created
• We improved the validation handling inside workflow function configurations
• We improved the Copy Field Values post function, where now the CWX Issue Picker custom field is supported
• We fixed a Bug in our Required Fields validator, where Conditions couldn't be removed, once configured
• We fixed a Bug in our User in Project Role(s) condition and validator, where renaming a project role lead to an error
• We fixed a Bug in our Copy Field Value(s) between related Issues post function, where a configuration for a sub-task lead to an error when executed in a regular issue

• We added a new post function "Copy Field Value(s) between related Issues" that copies values between related issues on a transition. It supports Parent/Sub-task and Epic/Story relations in both directions.
• We set two post functions to deprecated (Copy Field Value From Sub-Task to Parent Issue & Copy Field Value From Parent Issue to Sub-Task) as they are both included in our new post function "Copy Field Value(s) between related Issues".
• We fixed a Bug, where sometimes configured default values stayed on the screen after switching to an issue type without a default value.
• We fixed a Bug, where values changed by our post functions could not be re-used in following post functions.
• We fixed a Bug, where options in "Copy Field Value" Post Function were empty

• We fixed a bug, where special characters in individual error messages where not unescaped when displayed to the user
• We fixed a bug in User In Field condition/validator, where single user custom fields did not work properly

• We fixed a Bug, where the Required Field Validator did not work correctly when the Scriptrunner App was installed
• We fixed a Bug, where some operators did not work in combination with single select and radio custom fields
• We fixed a Bug, where some WES functions could not be deleted after a configured custom field got deleted
• We fixed a Bug, where default values didn’t work on specific create screens

• New post function: "Clear Field Value(s)" to clear any field values on a transition
• Improvement of "User in Field" condition/validator: you can now choose from multiple fields and decide between "all", "none" or "at least in one" functions
• Improvement of the conditional feature inside the "Required Fields" validator: Conditions now get loaded with full JavaScript functionality
• We fixed a bug inside "Create a new Linked Issue" post function, where already saved issue types that are not available anymore, were not shown as errors to to the Admin
• We fixed a bug inside "Field Compare" condition/validator, where fields provided by other Apps could not be used

Happy New Year 2020!We are thrilled to provided you with a new version of Workflow Essentials, including the following features:

• We extended the "Required Fields" Validator with a conditional execution. Please try it out and let us know what you think. We might add this feature to other Validators and Post Functions.
• We changed some UI elements to integrate better with Jira's standard UI.
• We improved the existing "User in Field Condition/Validator" to check also for groups, configured in a custom field.
• We fixed a bug where the Resolution field didn't work as expected.

• We fixed a Bug, where the error message for the Copy Fields post-function was misleading
• We fixed a Bug in User in Group condition/validator, where group names including commas were not working correctly

• we fixed a bug, where fields with default values were not cleared after switching the issue type to one without default values (PBT-66)

• Compatibility to Jira 8.4.x
• We fixed a bug in Field Compare Validator/Condition, where multiple values for Option ID's were not possible to configure
• We fixed a bug in Required Fields Validator, where Tempo "Account" custom field was not treated as empty
• For better performance at startup we no longer check existing workflows for deprecated functions. Deprecated functions now always get disabled. Read more about deprecated functions in our documentation.
• Support for Scripted User custom field (by Misc Custom Fields App) in Assign to User specified in (Custom) Field Post Function
• Improved JQL Validator/Condition to handle nested queries

• support of user and multi-user fields in Field Compare Validator
• support of Misc Custom Field calculated user field in Field Compare Validator
• general support of original estimate and remaining estimate system fields in copy functions

• Support of "Secure Fields" User Custom Field types
• New operator "CONTAINS" for Field Compare Validator/Condition

• new Validator/Condition: validate the current issue against a JQL expression
• Bugfix: we fixed a Bug where "Time Spent" was not handled correctly in the Required Fields Validator

• Minor Bugfixes

• Issue Types in Create and Link Post Function are now translated
• IN and NOT IN operators in Field Compare Validator and Condition now work with Single Select Custom Fields
• IN and NOT IN operators in Field Compare Validator and Condition now work with Numeric Fields
• Bugfix: IN operator in Field Compare Validator and Condition didn't work as expected

Please note that this version of Workflow Essentials is compatible with Jira from version 7.6.0 to 7.13.X. Those versions have reached their end of life. Please update to the latest 8.x.x version and the corresponding Workflow Essentials version.

• we fixed a bug in our "Transition Linked Issue" post function, where older configurations were broken due to missing legacy handling

• we improved our "User in Group" condition/validator to check for negated result
• we improved our "User in Project Role" condition/validator to check for negated results
• we improved our "Transition linked Issues" post function to copy fields during the transition

• We fixed a bug, where assigning an issue didn't work due to lacking user permission

• We fixed a bug, where setting the assignee during issue creation didn't work properly
• We improved our "Create a new linked Issue" post function to handle Portfolio hierarchies
• We improved our "Create a new linkes Issue" post function to create issues in several projects by supporting the selection in a Multi Picker custom field

• We fixed a bug, where the IN operator didn't work for multiple Resolutions in our Field Value condition/validator
• We fixed a bug in our "Update/Set Field to predefined value" post function, where Multi Group picker was not supported
• We fixed a bug, where the initial save of our "Create a new Linked Issue" post function was not working
• We added the "Created" system field as a source in our "Copy Field Value" post function

• We improved the error message in our Create and Link post function, to give the user a better explanation what went wrong , when a new issue can not be created
• We improved the validation handling inside workflow function configurations
• We improved the Copy Field Values post function, where now the CWX Issue Picker custom field is supported
• We fixed a Bug in our Required Fields validator, where Conditions couldn't be removed, once configured
• We fixed a Bug in our User in Project Role(s) condition and validator, where renaming a project role lead to an error
• We fixed a Bug in our Copy Field Value(s) between related Issues post function, where a configuration for a sub-task lead to an error when executed in a regular issue

• We added a new post function "Copy Field Value(s) between related Issues" that copies values between related issues on a transition. It supports Parent/Sub-task and Epic/Story relations in both directions.
• We set two post functions to deprecated (Copy Field Value From Sub-Task to Parent Issue & Copy Field Value From Parent Issue to Sub-Task) as they are both included in our new post function "Copy Field Value(s) between related Issues".
• We fixed a Bug, where sometimes configured default values stayed on the screen after switching to an issue type without a default value.
• We fixed a Bug, where values changed by our post functions could not be re-used in following post functions.
• We fixed a Bug, where options in "Copy Field Value" Post Function were empty

• We fixed a bug, where special characters in individual error messages where not unescaped when displayed to the user
• We fixed a bug in User In Field condition/validator, where single user custom fields did not work properly

• We fixed a Bug, where the Required Field Validator did not work correctly when the Scriptrunner App was installed
• We fixed a Bug, where some operators did not work in combination with single select and radio custom fields
• We fixed a Bug, where some WES functions could not be deleted after a configured custom field got deleted
• We fixed a Bug, where default values didn’t work on specific create screens

• New post function: "Clear Field Value(s)" to clear any field values on a transition
• Improvement of "User in Field" condition/validator: you can now choose from multiple fields and decide between "all", "none" or "at least in one" functions
• Improvement of the conditional feature inside the "Required Fields" validator: Conditions now get loaded with full JavaScript functionality
• We fixed a bug inside "Create a new Linked Issue" post function, where already saved issue types that are not available anymore, were not shown as errors to to the Admin
• We fixed a bug inside "Field Compare" condition/validator, where fields provided by other Apps could not be used

Happy New Year 2020!

We are thrilled to provided you with a new version of Workflow Essentials, including the following features:

• We extended the "Required Fields" Validator with a conditional execution. Please try it out and let us know what you think. We might add this feature to other Validators and Post Functions.
• We changed some UI elements to integrate better with Jira's standard UI.
• We improved the existing "User in Field Condition/Validator" to check also for groups, configured in a custom field.
• We fixed a bug where the Resolution field didn't work as expected.

• We fixed a Bug, where the error message for the Copy Fields post-function was misleading
• We fixed a Bug in User in Group condition/validator, where group names including commas were not working correctly

• we fixed a bug, where fields with default values were not cleared after switching the issue type to one without default values (PBT-66)

• We fixed a bug with Default Values, where values of rich-text editor fields where not set when placed on tabs
• We fixed a bug in Field Compare Validator/Condition, where multiple values for Option ID's were not possible to configure
• We fixed a bug in Required Fields Validator, where Tempo "Account" custom field was not treated as empty
• For better performance at startup we no longer check existing workflows for deprecated functions. Deprecated functions now always get disabled. Read more about deprecated functions in our documentation.
• Support for Scripted User custom field (by Misc Custom Fields App) in Assign to User specified in (Custom) Field Post Function
• Improved JQL Validator/Condition to handle nested queries

• support of user and multi-user fields in Field Compare Validator
• support of Misc Custom Field calculated user field in Field Compare Validator
• general support of original estimate and remaining estimate system fields in copy functions

• Support of "Secure Fields" User Custom Field types
• New operator "CONTAINS" for Field Compare Validator/Condition

• new Validator/Condition: validate the current issue against a JQL expression
• Bugfix: we fixed a Bug where "Time Spent" was not handled correctly in the Required Fields Validator

• Improved Comment Issue Post Function:
  • comments can now be made for specific users
  • comments can be made as Internal in Service Desks
• Improved Gateway Post Function:
  • error message can now be customized
• Bugfixes:
  • https://service.atlassian.codecentric.de/browse/PBT-59
  • https://service.atlassian.codecentric.de/browse/PBT-60

• We fixed a bug, where default values were not always replaced in rich text editors

Includes all bugfixes and new features of the last year, compatible to older Jira versions (7.1.1 - 7.5.4). Please note that your Jira version reached end of life. You should update to a newer version soon.

• Minor Bugfixes

• Issue Types in Create and Link Post Function are now translated
• IN and NOT IN operators in Field Compare Validator and Condition now work with Single Select Custom Fields
• IN and NOT IN operators in Field Compare Validator and Condition now work with Numeric Fields
• Bugfix: IN operator in Field Compare Validator and Condition didn't work as expected

• Bugfix: removed Cascading List Custom Fields from selection in Field Compare Validator, as it is not supported.
• Bugfix: Set Custom Field to predefined value Post Function now supports Labels Custom Fields.