Minor version update

Improvements:

• Extended macro support for referencing fields

Read more in the full release notes.

Improvements:

• Extended macro support for referencing fields

Read more in the full release notes.

Updates

• Compatibility for Jira 9.7.0

Updates

• Compatibility for Jira 9.7.0

Bug fixes

• Fixed an issue with JSU’s implementation of the Configuration Manager for Jira SPI during the deployment of the Linked Transition (JSU) post function

Updates

• Upgraded the FasterXML Jackson databind (com.fasterxml.jackson.core) to resolve security vulnerability CVE-2022-42003

Bug fixes

• Fixed an issue with JSU’s implementation of the Configuration Manager for Jira SPI during the deployment of the Linked Transition (JSU) post function

Updates

• Upgraded the FasterXML Jackson databind (com.fasterxml.jackson.core) to resolve security vulnerability CVE-2022-42003

• Correction to the placement of an asterisk in the JSU Fields Required validator UI
• Fixed an issue where fields persisted after removing them from the Clear Field Value (JSU) post function
• Fixed an issue where expected fields were not copied to a subtask that was created from a post function

• Correction to the placement of an asterisk in the JSU Fields Required validator UI
• Fixed an issue where fields persisted after removing them from the Clear Field Value (JSU) post function
• Fixed an issue where expected fields were not copied to a subtask that was created from a post function

Bug fixes

• Fixed an issue with the Activity tab sort order for transitions.
• Fixed an issue that resulted in some fields not updating if the JQL Condition was used for the Update Any Issue Field post function.

Improvements

• Enhanced compatibility for fields from third-party apps.

Read more in the full release notes.

Bug fixes

• Fixed an issue with the Activity tab sort order for transitions.
• Fixed an issue that resulted in some fields not updating if the JQL Condition was used for the Update Any Issue Field post function.

Improvements

• Enhanced compatibility for fields from third-party apps.

Read more in the full release notes.

Bug fixes

• Fixed an issue with the Fields Required validator where a required field for Attachment returned an error even when the transitioning issue had attachments: additional scenarios where the bug was encountered are now resolved.

Improvements

• Update Any Issue Field post function: Added support to set a field value to the previous user assigned to a field. If you select a single-user picker field such as Assignee, Reporter, or a custom field, you can set the value to %%PREVIOUS_USER%%.
• Update/Copy field value: Added support to parse the unit defined in Time Tracking Configuration.

Read more in the full release notes.

Bug fixes

• Fixed an issue with the Fields Required validator where a required field for Attachment returned an error even when the transitioning issue had attachments: additional scenarios where the bug was encountered are now resolved.

Improvements

• Update Any Issue Field post function: Added support to set a field value to the previous user assigned to a field. If you select a single-user picker field such as Assignee, Reporter, or a custom field, you can set the value to %%PREVIOUS_USER%%.
• Update/Copy field value: Added support to parse the unit defined in Time Tracking Configuration.

Read more in the full release notes.

• Bug Fix
  • Fixed an issue with the Fields Required validator where a required field for Attachment returned an error even when the transitioning issue had attachments
• Updates
  • Updated brand references and documentation links in line with Appfire brand initiative

• Bug Fix
  • Fixed an issue with the Fields Required validator where a required field for Attachment returned an error even when the transitioning issue had attachments
• Updates
  • Updated brand references and documentation links in line with Appfire brand initiative

See the full list of features and fixes in our release notes for 2.34.0

See the full list of features and fixes in our release notes for 2.34.0

https://beecom-products.atlassian.net/l/c/WtaGqaZL

https://beecom-products.atlassian.net/l/c/WtaGqaZL

https://beecom-products.atlassian.net/l/c/0AHNC1aW

https://beecom-products.atlassian.net/l/c/0AHNC1aW

JSU 2.32.0 will be compatible with Atlassian’s Jira Cloud Migration Assistant (v1.6.3 or above) for performing app-migrations.

You’ll be able to automatically migrate most of your JSU workflow automations from your Server/Data Center instance to your Cloud instance

Read more at: https://beecom-products.atlassian.net/l/c/tprYRvSP

JSU 2.32.0 will be compatible with Atlassian’s Jira Cloud Migration Assistant (v1.6.3 or above) for performing app-migrations.

You’ll be able to automatically migrate most of your JSU workflow automations from your Server/Data Center instance to your Cloud instance

Read more at: https://beecom-products.atlassian.net/l/c/tprYRvSP

Anonymized analytics

https://beecom-products.atlassian.net/l/c/LuFPf0ZA

Anonymized analytics

https://beecom-products.atlassian.net/l/c/LuFPf0ZA

https://beecom-products.atlassian.net/l/c/MUfegsTc

https://beecom-products.atlassian.net/l/c/MUfegsTc

New Feature

• You can now add internal (private) comments to your Service Project issues! The feature applies to “Create Linked Issue,” “Update Any Field,” and “Copy Value From Other Field” post-functions

Bug Fix

• Fixed an issue where setting/appending multiple values to the Label field did not work as expected

New Feature

• You can now add internal (private) comments to your Service Project issues! The feature applies to “Create Linked Issue,” “Update Any Field,” and “Copy Value From Other Field” post-functions.

Bug Fix

• Fixed an issue where setting/appending multiple values to the Label field did not work as expected.

Improvements

• Botron's CMJ Integration: Improvement in converting of configuration of post functions.
• Ability to add line-feed at the end of multi-line text field.

Improvements

• Botron's CMJ Integration: Improvement in converting of configuration of post functions.
• Ability to add line-feed at the end of multi-line text field.

New Feature

• JSU 2.27.0 introduces the integration support for Configuration Manager for Jira (CMJ) by Botron. The integration enables the migration of all JSU configurations including global settings, project variables, custom fields, conditions, validators, and post-functions with CMJ. More details

Bug Fix

• Fixed an issue where the Set value of *** new comment *** for a new issue in Create A Linked Issue post-function is not working

New Feature

• JSU 2.27.0 introduces the integration support for Configuration Manager for Jira (CMJ) by Botron. The integration enables the migration of all JSU configurations including global settings, project variables, custom fields, conditions, validators, and post-functions with CMJ. More details

Bug Fix

• Fixed an issue where the Set value of *** new comment *** for a new issue in Create A Linked Issue post-function is not working

Improvements

• When the CreateLinkedIssue SetFieldValue Sub-function is set with the %%CURRENT_DATETIME%% macro value, a target DateTime CustomField will be correctly set.
• When copying to the labels target field, spaces in source values will be replaced with an underline.
• JSU Location Text Custom Field view properly encodes UTF-8 characters.
• "Update any Issue Field" and "Copy Value From Other Field / Linked Transition" post-functions behave consistently. When in "Overwrite" mode the "*** empty ***" source value is handled as the value null and in "Append/Prepend" mode the "*** empty ***" source value is handled as an empty string.

Improvements

• When the CreateLinkedIssue SetFieldValue Sub-function is set with the %%CURRENT_DATETIME%% macro value, a target DateTime CustomField will be correctly set.
• When copying to the labels target field, spaces in source values will be replaced with an underline.
• JSU Location Text Custom Field view properly encodes UTF-8 characters.
• "Update any Issue Field" and "Copy Value From Other Field / Linked Transition" post-functions behave consistently.

Improvements

• More robust handling when converting comma delimited text values to multi- group or user custom fields.
• Sorting cascading select options by hierarchy then by name when joining as string value in “Regular Expression Check Validator (JSU)“.
• Prevent setting a value to the “Epic Link” field on a SubTask.
• AUI 9 compatibility.

Improvements

• More robust handling when converting comma delimited text values to multi- group or user custom fields.
• Sorting cascading select options by hierarchy then by name when joining as string value in “Regular Expression Check Validator (JSU)“.
• Prevent setting a value to the “Epic Link” field on a SubTask.
• AUI 9 compatibility.

Bugfixes

• Conditions and validators now properly resolve the “Security Level” system field value.
• “Copy Value From Other Field (JSU)” allows for custom fields copy from more 3rd party apps.
• “Create a Linked Issue (JSU)” allows the copy of the third party “Multi-Level Cascading Select” custom field options if multiple options exist with the same name.

Bugfixes

• Conditions and validators now properly resolve the “Security Level” system field value.
• “Copy Value From Other Field (JSU)” allows for custom fields copy from more 3rd party apps.
• “Create a Linked Issue (JSU)” allows the copy of the third party “Multi-Level Cascading Select” custom field options if multiple options exist with the same name.

Bugfixes

• “Update Any Issue Field (JSU)” fixed for Sprint field.
• “Linked Transition (JSU)” fixed some issue with comments.

Improvements

• “Regular Expression Check Validator” & “Regular Expression Check Precondition” are now more flexible with multiple value / multi-line fields.
• More 3rd party custom field types supported (i.e. “Multi-Level Cascading Select”).
• “Transition Trigger Service” can now also handle workflows with global transitions (which did not change the issue status).

Bugfixes

• “Update Any Issue Field (JSU)” fixed for Sprint field.
• “Linked Transition (JSU)” fixed some issue with comments.

Improvements

• “Regular Expression Check Validator” & “Regular Expression Check Precondition” are now more flexible with multiple value / multi-line fields.
• More 3rd party custom field types supported (i.e. “Multi-Level Cascading Select”).
• “Transition Trigger Service” can now also handle workflows with global transitions (which did not change the issue status).

Bugfixes

• The “Clear Field Value (JSU)” post-function edit dialog did not function correctly.
• The “Update Any Issue Field (JSU)” post-function execution failed when set to “Clear” (no value).
• JSU post functions which were configured to copy an issue constant (i.e. IssueType, Priority, Resolution ,Status) to a Select custom field type would fail.

Bugfixes

• The “Clear Field Value (JSU)” post-function edit dialog did not function correctly.
• The “Update Any Issue Field (JSU)” post-function execution failed when set to “Clear” (no value).
• JSU post functions which were configured to copy an issue constant (i.e. IssueType, Priority, Resolution ,Status) to a Select custom field type would fail.

New Features

Added a "Status Changed" workflow condition and precondition.

Improvements

"Update Any Issue Field" time tracking fields now accept literal duration format (i.e. "1w 2d 3h").

If Timespent is specified as a target field, work logs are added or removed to keep "Time Tracking" consistent with work logs.

The "JSU Bulk Copy" operation no longer attempts to copy time tracking fields to the target issue/s.

Improvements in "JSU Bulk Copy" operation custom field error handling.

Improvements validating multiline text fields with regular expressions.

Added a placeholder to all JQL configuration expression texts to improve intention of issue context restriction.

Bugfixes

In some Jira/Service Desk version constellations, an error occurred while copying the "Request Type" field in a "Create Linked Issue" post-function or assigning an "Organization" in an "Update Any Issue" post-function.

The "watchers" system field was not copied in a "Create Linked Issue" post-function.

New Features

• Added a "Status Changed" workflow condition and precondition.

Improvements

• "Update Any Issue Field" time tracking fields now accept literal duration format (i.e. "1w 2d 3h").
• If Timespent is specified as a target field, work logs are added or removed to keep "Time Tracking" consistent with work logs.
• The "JSU Bulk Copy" operation no longer attempts to copy time tracking fields to the target issue/s.
• Improvements in "JSU Bulk Copy" operation custom field error handling.
• Improvements validating multiline text fields with regular expressions.
• Added a placeholder to all JQL configuration expression texts to improve intention of issue context restriction.

Bugfixes

• In some Jira/Service Desk version constellations, an error occurred while copying the "Request Type" field in a "Create Linked Issue" post-function or assigning an "Organization" in an "Update Any Issue" post-function.
• The "watchers" system field was not copied in a "Create Linked Issue" post-function.

• Minor Security Improvements
• Updated Links to the new Documentation

• Minor Security Improvements
• Updated Links to the new Documentation

Bug fix

• Fixed issue with 'All other sibling issues must have on of the following statuses' check in the Linked Transition.
• Fixed diverse copy field related issues on the Create Linked Issue Post-Function.

Improvements

• Security improvements

Bug fix

• Fixed issue with 'All other sibling issues must have on of the following statuses' check in the Linked Transition.
• Fixed diverse copy field related issues on the Create Linked Issue Post-Function.

Improvements

• Security improvements

Bug fix

• Fiexed: In some cases, the Create Linked Issue Post-Function could not create a new issue with an error message about the reporter.

Bug fix

• Fiexed: In some cases, the Create Linked Issue Post-Function could not create a new issue with an error message about the reporter.

Improvement

• Fixed diverse copy field related issues on the "Create linked Issue" post function.
• Fixed an issue when copying Sprint into another issue.

Improvement

• Fixed diverse copy field related issues on the "Create linked Issue" post function.
• Fixed an issue when copying Sprint into another issue.

Improvement

• In some cases, the Create Linked Issue Post Function could not be displayed properly

Improvement

• In some cases, the Create Linked Issue Post Function could not be displayed properly

New Feature

• JSU 2.22.0 introduces the Fields Configuration section in the Create Linked Issue Post-Function. Use it to define configurations in order to modify fields on the origin and new issue.

New Feature

• JSU 2.22.0 introduces the Fields Configuration section in the Create Linked Issue Post-Function. Use it to define configurations in order to modify fields on the origin and new issue.

Improvements

• Security improvements

Improvements

• Security improvements

Improvement

• Links of Preconditions Documentation.
• Improved UI if Role is deleted in User in any Roles.
• Copying Labels is now possible in different post-functions

Improvement

• Links of Preconditions Documentation.
• Improved UI if Role is deleted in User in any Roles.
• Copying Labels is now possible in different post-functions.

New Features

We've implemented a new feature, which was requested by many JSU customers:

• Update Any Issue Field post function: Can now also be used to create a new comment on an issue.

Improvement

• Better support for 'perform as user'.

Bugfix

• Update Any Issue Field post function Fixed: duplicated change history entries that could happen when using an Oracle database for Jira.
• Copy Value From Other Field Post-Function Fixed: In a special case, perform as user field value was not properly saved.
• Fixed: Perform as user was not properly working, if the user id started with a dollar sign.

New Features

We've implemented a new feature, which was requested by many JSU customers:

• Update Any Issue Field post function: Can now also be used to create a new comment on an issue.

Improvement

• Better support for 'perform as user'.

Bugfix

• Update Any Issue Field post function Fixed: duplicated change history entries that could happen when using an Oracle database for Jira.
• Copy Value From Other Field Post-Function Fixed: In a special case, perform as user field value was not properly saved.
• Fixed: Perform as user was not properly working, if the user id started with a dollar sign.

New Feature

• JSU now has a Get Started tutorial.

Improvement

• Field Required Validator: Now shows a red asterisk * next to mandatory Attachment field in transition screens.
• We've improved the "Map Configuration" page in the Jira administration.
• Update Any Issue Field post function: If you use an unsupported macro, JSU now shows a better error message.

Bugfix

• Update Any Issue Field post function: Removing watcher is now working in the Edit mode.

New Feature

• JSU now has a Get Started tutorial.

Improvement

• Field Required Validator: Now shows a red asterisk * next to mandatory Attachment field in transition screens.
• We've improved the "Map Configuration" page in the Jira administration.
• Update Any Issue Field post function: If you use an unsupported macro, JSU now shows a better error message.

Bugfix

• Update Any Issue Field post function: Removing watcher is now working in the Edit mode.

• We extended the 'perform as user' functionality to all Post-Functions. You can now perform an Update in an other Project without having the permission, you can use a technical user (impersonation) instead. Perfect fit between a Developer & Service-Desk Project.
• new Condition 'User in Any Users': this works best together with the 'perform as user' functionality! You can hide the transition from all user except a technical user, which perform the transition.
• Issue Relation for Clear Field Value Post-Function: we introduced this well-known functionality from other Post-Function. For example, you can clear a field in all Sub-Tasks.

• We extended the 'perform as user' functionality to all Post-Functions. You can now perform an Update in an other Project without having the permission, you can use a technical user (impersonation) instead. Perfect fit between a Developer & Service-Desk Project.
• new Condition 'User in Any Users': this works best together with the 'perform as user' functionality! You can hide the transition from all user except a technical user, which perform the transition.
• Issue Relation for Clear Field Value Post-Function: we introduced this well-known functionality from other Post-Function. For example, you can clear a field in all Sub-Tasks.

Improvement

• Japanese translation of JQL field. A special thanks goes to Ricksoft who provided us the Japanese translations.
• Copying of some fields to a comment has been improved, resulting in better looking text in the comment.

Improvement

• Japanese translation of JQL field. A special thanks goes to Ricksoft who provided us the Japanese translations.
• Copying of some fields to a comment has been improved, resulting in better looking text in the comment

Improvement

• You can now limit the maximum number of issues found by JQL in our post functions.

Bugfixes

• Better support for Jira Service Desk fields.

Improvement

• You can now limit the maximum number of issues found by JQL in our post functions.

Bugfixes

• Better support for Jira Service Desk fields.

Improvement

Better support of Jira Software fields in the jql conditions, pre-conditions and scope.

Bugfix

some minor bug-fix while updating or cloning issue

Improvement

Better support of Jira Software fields in the jql conditions, pre-conditions and scope.

Bugfix

some minor bug-fix while updating or cloning issue

New feature:

We built a JQL Condition, JQL Precondition and integrated JQL in many Workflow Post-Functions, allowing advanced administrators to set wider parameters that may now be fully customized.

New functionalities:

• Create unlimited JQL-based conditions.
• Even combine multiple pre-conditions into one.
• Define post-function targets with JQL

Bugfixes:

• Field required marker (red asterisk) was missing on the Attachment field in different languages.
• Users in any role condition edit after the role is deleted had a problem which we have already fixed.

New feature:

We built a JQL Condition, JQL Precondition and integrated JQL in many Workflow Post-Functions, allowing advanced administrators to set wider parameters that may now be fully customized.

New functionalities:

• Create unlimited JQL-based conditions.
• Even combine multiple pre-conditions into one.
• Define post-function targets with JQL

Bugfixes:

• Field required marker (red asterisk) was missing on the Attachment field in different languages.
• Users in any role condition edit after the role is deleted had a problem which we have already fixed.

Improvement

Better support of Jira Service Desk fields in the conditions.

Summary and environment can be used in a more efficient way now.

Improvement

Better support of Jira Service Desk fields in the conditions.

Summary and environment can be used in a more efficient way now.

New Feature

We've implemented a powerful new feature, which was requested by many JSU customers:

• JSU's workflow modules (conditions, validators, post functions) work even better with Jira Service Desk: Now JSU Customers can use JSU to update Customer Request type, Organisation and Request Participants in Jira Service desk.

Improvements

• Copy 'Original Estimate' field to a text field.
• 'Create new version if necessary' now also works, when the source field is not a version field, but just a text, select, etc. field.

New Feature

We've implemented a powerful new feature, which was requested by many JSU customers:

• JSU's workflow modules (conditions, validators, post functions) work even better with Jira Service Desk: Now JSU Customers can use JSU to update Customer Request type, Organisation and Request Participants in Jira Service desk.

Improvements

• Copy 'Original Estimate' field to a text field.
• 'Create new version if necessary' now also works, when the source field is not a version field, but just a text, select, etc. field.

Copying attachments from the transition screen is now working in Jira 8.0.0 and higher. Create a Linked Issue and Copy or Move Attachments Post-Function had been affected by this.

Copying attachments from the transition screen is now working in Jira 8.0.0 and higher. Create a Linked Issue and Copy or Move Attachments Post-Function had been affected by this.

• Create Linked Issue post function: Project picker custom field type can now also be used, to let the end user choose the target project.
• Create Linked Issue post function: It is now also possible to copy a value to the Original Estimate field on the new issue.
• Linked Transition post function: Copy transition comment to the related issue is now configured in the copy field section, the same as in other post functions.

• Create Linked Issue post function: Project picker custom field type can now also be used, to let the end user choose the target project.
• Create Linked Issue post function: It is now also possible to copy a value to the Original Estimate field on the new issue.
• Linked Transition post function: Copy transition comment to the related issue is now configured in the copy field section, the same as in other post functions.

Improvements

• JSU changed its name to JSU Automation Suite for Jira Workflows because its all about automation
• Create Linked Issue has new more intuitive GUI for "Target Project" & Target Issue Type defined by custom field selection
• Several minor internal cleanups

For further details please go to full release notes

Improvements

• JSU changed its name to JSU Automation Suite for Jira Workflows because its all about automation
• Create Linked Issue has new more intuitive GUI for "Target Project" & Target Issue Type defined by custom field selection
• Several minor internal cleanups

For further details please go to full release notes

New Features

We've implemented a powerful new feature, which was requested by many JSU customers:

• Create Linked Issue post function: Now it's possible, that the end user can choose the target project and/or issue type for the new issue! Basically, as Jira admin, you defined a custom field on the transition screen, which will control the target project/issue type. For example, you might use a Project Picker for this, or a Select List with only a few preconfigured projects.

Improvements

• Linked Status validator allows to set custom error message

Bugfixes

• Create Linked Issue priority is not properly displayed in the workflow configuration
• Field Required Validator does not display error message for comment field provided by Jira Service Desk (since version 2.5.0)
• Precondition Value Field doesn't work for issue picker field type (especially Epic Link field)

For further details please go to full release notes

New Features

We've implemented a powerful new feature, which was requested by many JSU customers:

• Create Linked Issue post function: Now it's possible, that the end user can choose the target project and/or issue type for the new issue! Basically, as Jira admin, you defined a custom field on the transition screen, which will control the target project/issue type. For example, you might use a Project Picker for this, or a Select List with only a few preconfigured projects.

Improvements

• Linked Status validator allows to set custom error message

Bugfixes

• Create Linked Issue priority is not properly displayed in the workflow configuration
• Field Required Validator does not display error message for comment field provided by Jira Service Desk (since version 2.5.0)
• Precondition Value Field doesn't work for issue picker field type (especially Epic Link field)

For further details please go to full release notes

Improvements

• Post function Copy / Move Attachments does not duplicate existing attachments (both for existing & transition attachments)

Bugfixes

• Fixed a problem of Create A Linked Issue post function which did not copy/move transition attachment base on a field value
• Fixed a problem of Create A Linked Issue post function which failed if executed through a Trigger (e.g. Bitbucket Commit Created)
• Deleted custom fields do not break the view in workflow administration
• After modifying value of "Time Spent" field history change is properly added. Affected modules: Clear Field Value post function and Update Any Issue Field post function

For further details please go to full release notes

Improvements

• Post function Copy / Move Attachments does not duplicate existing attachments (both for existing & transition attachments)

Bugfixes

• Fixed a problem of Create A Linked Issue post function which did not copy/move transition attachment base on a field value
• Fixed a problem of Create A Linked Issue post function which failed if executed through a Trigger (e.g. Bitbucket Commit Created)
• Deleted custom fields do not break the view in workflow administration
• After modifying value of "Time Spent" field history change is properly added. Affected modules: Clear Field Value post function and Update Any Issue Field post function

For further details please go to full release notes

New Feature

• The new post function "Copy / Move Attachments" allows you to copy attachments from/to all related issues.

Improvements

• JSU now can be used completely in Japanese. A special thanks goes to Ricksoft who provided us the Japanese translations.
• "Error message (optional):" parameter was removed from all workflow preconditions. (Since it is only used for validators.)
• Log entries generated by JSU are more descriptive.
• Better error messages for Linked Transition post function in case the desired transition cannot be performed.

For further details, see the full release notes.

New Feature

• The new post function "Copy / Move Attachments" allows you to copy attachments from/to all related issues.

Improvements

• JSU now can be used completely in Japanese. A special thanks goes to Ricksoft who provided us the Japanese translations.
• "Error message (optional):" parameter was removed from all workflow preconditions. (Since it is only used for validators.)
• Log entries generated by JSU are more descriptive.
• Better error messages for Linked Transition post function in case the desired transition cannot be performed.

For further details, see the full release notes.

• Fixed a problem of the Transition Trigger Service in combination with Workflow Conditions.
• After dis-/enabling or updating JSU, it is no more necessary to restart Jira to get the Transition Trigger Service working again.

For further details please go to full release notes

• Fixed a problem of the Transition Trigger Service in combination with Workflow Conditions.
• After dis-/enabling or updating JSU, it is no more necessary to restart Jira to get the Transition Trigger Service working again.

For further details please go to full release notes

Improvements

• The following three calculated system fields are now also supported (read-only):
  • Aggregated (Sum) Original Estimate
  • Aggregated (Sum) Remaining Estimate
  • Aggregated (Sum) Time Spent
• Additional special sources (default value & empty) for the "Copy from the Origin Issue to the New Issue" section in the Create a Linked Issue post function.
• Update any Issue Field Post-Function improved for the Watcher system field.
• Better support for the Update any Issue Field Post-Function in the create transition.
• Copy Value From Other Field Post-Function now behaves better during the clone issue operation (which is a special case of the create transition).
• Removed some fields from the Clear Field Value Post-Function configuration screen, which could not have been cleared anyway. (Like Issue Key, Project, Status, etc.)

Bugfixes

Several bugs have been fixed.

For further details, see the full release notes.

Improvements

• The following three calculated system fields are now also supported (read-only):
  • Aggregated (Sum) Original Estimate
  • Aggregated (Sum) Remaining Estimate
  • Aggregated (Sum) Time Spent
• Additional special sources (default value & empty) for the "Copy from the Origin Issue to the New Issue" section in the Create a Linked Issue post function.
• Update any Issue Field Post-Function improved for the Watcher system field.
• Better support for the Update any Issue Field Post-Function in the create transition.
• Copy Value From Other Field Post-Function now behaves better during the clone issue operation (which is a special case of the create transition).
• Removed some fields from the Clear Field Value Post-Function configuration screen, which could not have been cleared anyway. (Like Issue Key, Project, Status, etc.)

Bugfixes

Several bugs have been fixed.

For further details, see the full release notes.

Improvements

• Limits for Bulk Copy to prevent high load on a Jira instance.Number of issues that can be copied are limited.Number of simultaneous running Bulk Copy jobs are limited.Both limits can be changed by an administrator.
• Further improvements on Bulk Copy to optimise scalability.

Bugfixes

• Required tab asterisk fixed for Internet Explorer
• Workaround for JRASERVER-67797 to display workflow validator messages during issue clone operation.

Improvements

• Limits for Bulk Copy to prevent high load on a Jira instance.Number of issues that can be copied are limited.Number of simultaneous running Bulk Copy jobs are limited.Both limits can be changed by an administrator.
• Further improvements on Bulk Copy to optimise scalability.

Bugfixes

• Required tab asterisk fixed for Internet Explorer
• Workaround for JRASERVER-67797 to display workflow validator messages during issue clone operation.

Improvements

• Fields Required Validator: Red asterisk is now also shown on tabs, which contain required fields.
• Create a Linked Issue: Can now copy both - existing and transition - comments at once to the new issue.

Bugfixes

• Create a Linked Issue: Problem with renamed users fixed.
• Update any Issue Field Post-Function: Problem with renamed users in a 'User Picker (multiple users)' field fixed.
• Copy Value From Other Field Post-Function: Bug fixed when copying values between different cascading select fields.
• Bulk Copy: No more fails with the Participant field from the Toolkit plugin.

Preconditions for Post Functions

Resolve your most complex cases with the new JSU Preconditions.

Those are conditions or predicators that should always be true just prior to the execution of a post function. The result of a precondition can be used in a later post function to decide, if this post function will be executed at all or not.

Define your complex conditions directly in JIRA's workflow GUI easier.

• No complicated scripts.
• Users don't need to worry about complex business rules any more. Everything automated in the workflow with the new JSU.

Take your JIRA to the next level with JSU 2.5

Enjoy!

Bugfix

• Fixed issue 'Action xxx is invalid'

Preconditions for Post Functions

Resolve your most complex cases with the new JSU Preconditions.

Those are conditions or predicators that should always be true just prior to the execution of a post function. The result of a precondition can be used in a later post function to decide, if this post function will be executed at all or not.

Define your complex conditions directly in JIRA's workflow GUI easier.

• No complicated scripts.
• Users don't need to worry about complex business rules any more. Everything automated in the workflow with the new JSU.

Take your JIRA to the next level with JSU 2.5

Enjoy!

Bug in 2.5.0 has been fixed in 2.5.1

• Fixed issue with 'Fields Required' Validator in the 'Create Transition'.

Minor UI tweaks for the fresh, new look of Jira 7.10

• Fixed: Problem in some cases when a multi value field (e.g. Multi-Select User Picker) was empty.

• Fixed: Date Compare Validator & Date Expression Compare Validator had a problem, when 'Include time part' was not selected.

Make your work-life easier using the latest JSU Version

Adapted to the Atlassian design guidelines, JSU 2.4.0 is now offering a better experience and usability.

Update any Issue Field Post-Function

• Have you ever tried to update a component with a post function? With Jira's standard 'Update Issue Field' post function you couldn't.
• Have you ever tried to update any system field on a sub task using a post function on the parent issue? You probably failed.

Our 'Update any Issue Field (JSU)' post function now also covers system fields in addition to the previous custom fields.

Regular Expression Check Validator now supports even more fields

For example the system field Resolution is now also supported. Plus many other fields.

... and more

Small bug fixes and stability improvements.

See the full release notes at: https://confluence-apps.beecom.ch/display/JSU/JSU+2.4.0+Release+Notes

JSU now provides better support for comments, not only fields, of an issue.

We value the feedback of JSU users, which has helped us to further improve JSU and fix some bugs. Do you also have any comment for us or need some help with JSU? Please contact us at our service desk: https://servicedesk-apps.beecom.ch/servicedesk/customer/portal/3

New Feature

• Support of copy comments in 'Copy Value to other Field', 'Create Linked Issue' and 'Linked Transition' post functions.

Improvement

• Better support of multiple errors with 'Fields Required' Validator in the 'Create Transition'.

Bugfixes

• Show required * for 'Time Spent' field.
• Fix issue with Security Level Field in 'Copy Value to other Field' post function.
• Correct handling of comma-separated users in 'Update Issue Costom Field' post function.
• Issue Assignee is not correctly preselected in edit mode of 'Create Linked Issue' post function.

• Fixed correct handling of renamed user as assignee in the 'Linked Transition' Post-Function.
• Fixed a problem with the configuration page in the Jira administration.

• Fix configuration issue with 'User is in Custom Field' Condition.

In JSU 2.1.0 we introduced additional scopes on related issues to several post-functions like "Create Linked Issue" or "Copy Value From Other Field". We extended the same feature to "Update Issue Custom Field". With JSU 2.2.0 you are no longer restricted to only update a custom field inside the same issue. You will now also be able to update any linked issue either through Issue Linking, Parent/Sub-Task or Epic.

Issue Linking: We went even further and introduced the value ANY for 'Issue Link' definition. You have now the full flexibility to update a field, or copy a value to ANY 'Linked Issues', no matter of the type of link (e.g. related to / blocks / ...).

... and more small bug fixes, usability and stability improvements.

Improvements

• Security Level field type supported by Value Field Condition.
• Post functions can now append additional users to watchers of an issue.

Bugfix

• Fix for older versions of Internet Explorer, when configuring Related Issues.

• Fix issue with Clear Field Value Post-Function for Components

• Scope: Connect workflows of Sub-Tasks & Issues in Epic

In addition to linked Issues, you can create Sub-Tasks and Issues in Epics and trigger a transition on any relating Issue i.e. Issues in Parent/Sub-Tasks and Epic/Issue in Epic relation.

• Deal with permissions: Connect workflows of restricted projects

Teams need certain permissions to make the most out of "Create Linked Issue" & "Linked Transition". The new "…as User" feature allows to configure a technical user, which creates new Issues or triggers transitions on existing ones, where real users are restricted on.

• Many refinements on "Copy Value From Other Field"

Copy value from related Issue to Issue in transition

Copy from Issue in transition to related Issue

Copy any number of fields during single post function

App- / prepend copied value to any existing value

• Set own validation error messages

Implement any message, which provides actual information for your users.

See the full release notes

• Support for new Priority Schemes in Jira 7.6.0

• Minor bug fixes in the configuration of Linked Transition post function

More translations

• A special thanks goes to Ricksoft who provided us with Japanese translations of the app!
• One of our beecom employees from Spain contributed the Spanish translations.

Some of the newest JSU 2.0 features still lack any translation (english only). We plan to complete these in a later release.

Improvements

• Field Required Validator: Now shows a red asterisk * next to mandatory fields in the transition screens. One might not think that a small asterisk does need that much technical efforts to implement. That is why we never did it while JSU was provided as free app. With becoming commercial, and after many requests we wanted to serve the needs of our clients in a maximum way and implemented the little red star.

Bug fixes

• Linked Transition Post Function: The configuration will keep the correct name of the 'Transition'.
• Copy Value From Other Field Post Function: Now also works for cascading selects.

You're efficient within your team, but is your team efficient in working with other teams?

We proudly announce the new JSU 2.0, the biggest leap forward since we released version 1.0 in 2011 - it's finally possible to connect workflows of different teams in Jira.The new release includes additional and powerful post functions that make your daily work in Jira even more easy!

HERE ARE SOME NEW FUNCTIONS & FEATURES

• Create linked issues during transitions.
• Trigger a transition on a linked issue.
• Conditional flow in your workflow
• Bulk Copy

Since JSU has become a critical part for many Jira users, we want to match their expectations regarding quick, profound and professional support. To be able to provide such first class support, add more exiting new features and improvements, we decided to change JSU into a commercial add-on.

You're efficient within your team, but is your team efficient in working with other teams?

We proudly announce the new JSU 2.0, the biggest leap forward since we released version 1.0 in 2011 - it's finally possible to connect workflows of different teams in Jira.The new release includes additional and powerful post functions that make your daily work in Jira even more easy!

HERE ARE SOME NEW FUNCTIONS & FEATURES

• Create linked issues during transitions.
• Trigger a transition on a linked issue.
• Conditional flow in your workflow
• Bulk Copy

Since JSU has become a critical part for many Jira users, we want to match their expectations regarding quick, profound and professional support. To be able to provide such first class support, add more exiting new features and improvements, we decided to change JSU into a commercial add-on.

You're efficient within your team, but is your team efficient in working with other teams?

We proudly announce the new JSU 2.0, the biggest leap forward since we released version 1.0 in 2011 - it's finally possible to connect workflows of different teams in Jira.The new release includes additional and powerful post functions that make your daily work in Jira even more easy!

HERE ARE SOME NEW FUNCTIONS & FEATURES

• Create linked issues during transitions.
• Trigger a transition on a linked issue.
• Conditional flow in your workflow
• Bulk Copy

Since JSU has become a critical part for many Jira users, we want to match their expectations regarding quick, profound and professional support. To be able to provide such first class support, add more exiting new features and improvements, we decided to change JSU into a commercial add-on.

• [JSUTIL-344] - support data type Double for "append value"

• [JSUTIL-339] - jira suite utilites 1.5.2 configuration page not opening in jira 7.2.6

• [JSUTIL-325] - Location Text Field does not display a map
• [JSUTIL-322] - Copy Value From Other Field post function failing on user fields

• [JSUTIL-325] - Location Text Field does not display a map
• [JSUTIL-322] - Copy Value From Other Field post function failing on user fields

• [JSUTIL-275] - Custom field gets overwritten when append option is selected

• [JSUTIL-279] - Renaming a Username not synchronized between "History" and "Transitions"
• [JSUTIL-296] - Unable to set custom Project field in Post Function (1.5.0)
• [JSUTIL-302] - Date compare - French traduction
• [JSUTIL-308] - Transition with updated field with DateTime with append selected is inserting the new date rather than appending
• [JSUTIL-312] - Update Issue custom Field: problem with append values
• [JSUTIL-314] - Update Issue Custom Field - Append not working

• [JSUTIL-275] - Custom field gets overwritten when append option is selected

• [JSUTIL-279] - Renaming a Username not synchronized between "History" and "Transitions"
• [JSUTIL-308] - Transition with updated field with DateTime with append selected is inserting the new date rather than appending
• [JSUTIL-302] - Date compare - French traduction

• Transition tab no more using status icons.
• Several issues with Jira 7 compatibility fixed.

Jira Suite Utilities 1.5.0 Release Notes

Custom Fields

• JSUTIL-129: New custom field "Directions" (using Google Maps)
• JSUTIL-235: Location support GPS coordinates
• JSUTIL-65: New experimental custom field: Time in Source Status

Condition

• JSUTIL-17: "Value Field" supports date fields

Validators

• JSUTIL-229: "Regular Expression Check" supports select list, radio button & multi select fields
• JSUTIL-160: "Field Required", field contexts
• JSUTIL-233: "Field Required" new: "Σ Time Spent"
• JSUTIL-242: "Field Required" supports labels

Post Functions

• JSUTIL-25: "Copy Value From Other Field" GUI improved
• JSUTIL-236, JSUTIL-262: "Copy Value From Other Field" supports watchers
• JSUTIL-237: "Copy Value From Other Field" copy cascading select from parent
• JSUTIL-244: "Copy Value From Other Field" supports components
• JSUTIL-257: "Copy Value From Other Field" supports labels
• JSUTIL-202, JSUTIL-222, JSUTIL-201: "Update Issue Custom Field" append values
• JSUTIL-239: "Clear Field Value" supports labels

Others

• JSUTIL-254: Marked as data center compatibl

Bugfixes
JSUTIL-175, Entering values into custom fields before the issue is created creates an unlinked custom field value
JSUTIL-179, "Last Executer" for transition double HTML-escaped on Transitions Summary Tab
JSUTIL-183, Cannot edit workflow condition "User Is In Any Groups"
JSUTIL-192, Post Function to Update Cascading Select
JSUTIL-195, Cannot switch to Transitions Summary in IE9

Improvement:
JSUTIL-190, Transitions issue tab panel doesn't support ajax

Support Request:
JSUTIL-169, Cannot figure out the syntax to update a cascading select field during a transition.

Bugfixes:

JSUTIL-171, fixed javascript for IE8 Fields Required validator administration

JSUTIL-163, collections must also be checked if empty and compared to null

 JRA-32294 - Make the loading of Google Maps more robust. Check the 'reason' parameter from Jira.Events.NEW_CONTENT_ADDED before looking for maps

 JRA-32201 Fixes required for HTMLSafe compatability - Jira Suite Utilities 1.4.2

Bug Fix:

JRA-32201: Fixes required for HTMLSafe compatability

Bug Fix:

JRA-32296: Null Pointer Exception when Assignee is being cleared in a post function workflow transition.

Bug Fix

JRA-31864 XSS Vulnerabilities

Bug Fixes

JRA-31865 "User is in Custom Field" Condition evaluating incorrectly
JRA-31864 XSS Vulnerabilities
JRA-31862 Map for Location custom fields doesn't display to width of issue details panel in some browsers

JSUTIL-157 Option to append an entry to 'Update Issue Custom Field' transition when using a 'Multi User Picker Field' and %%CURRENT_USER%% value

Bug

• JSUTIL-155 Creating issues with FieldRequiredValidator set for FixVersions fails
  

Bug

• JSUTIL-137 Field Required Validator does not support validation of Version field having unarchived version selected.
• JSUTIL-151 Last Execution Time Not Timezone-Aware
  
• JSUTIL-152 Unable to copy from Assignee to the fixers field
  

Other

• French and german translation corrections
  

Bug

• JSUTIL-2 FieldsRequiredValidator uses hardcoded error messages so it cannot be localized via properties files

• JSUTIL-14 Window Dates Validator - Validator behaviour is different from UI text
• JSUTIL-16 Location Select List - Maps appear under the wrong issues in the issue navigator
• JSUTIL-21 User Is In Custom Field Condition - User cannot execute transition if the condition is "not in field" and the field is blank
• JSUTIL-24 Copy Value From Other Field Post Function - Copy fails for "Progress" field
• JSUTIL-28 Update Issue Custom Field Post Function - Cannot set multiple labels
• JSUTIL-30 Update Issue Field Post Function - Can update internal "Time Spent" field
• JSUTIL-31 Location Text Field / Location Select List - Location links are broken in Word export
• JSUTIL-32 Location Text Field / Location Select List - Location links are broken when viewed in a Filter Results gadget
• JSUTIL-121 Copy Value From Other Field for SelectCFType
• JSUTIL-126 FieldsRequiredValidator has incomplete error message on GreenHopper Classic New card screen
• JSUTIL-128 Location Text Field Google Maps fails on Chrome and IE8
• JSUTIL-131 View Validators in a transition not properly working for required field "Time spent"
• JSUTIL-143 Unable to update custom field in workflow post function

Improvement

• JSUTIL-8 All UI text is hardcoded as English
• JSUTIL-11 Location Select List - Cannot search by this field type
• JSUTIL-12 Review all UI text and improve clarity of instructions

Support Request

• JSUTIL-91 Spanish translations

JSU Location Fields to be compatible with Jira 5.1

+ Upgraded for Jira 5.1.
+ Cleaned up deprecated. …
~ Fixed drop down in configuration screen for field selection of post functions.
~ Fixed copy value post function to be able to copy assignee or other users to text field.

- JSUTIL-50
New macro %%CURRENT_DATETIME%% .

- JSUTIL-77
Setting (copying) values for system field Priorty supported.

- JSUTIL-87
Field Required Validator is now working for Cascading Select.

- JSUTIL-102
Setting user fixed.

- JSUTIL-104
Copy to Cascading Select now working.

- JSUTIL-105
Clear Field Value now working for Mulit User Picker.

- 'Deprecated' warnings reduced as much as possible.

See JRA-26785

JSUTIL-73

- JSUTIL-33
Field required: "time spent"

- JSUTIL-55
Better Option handling

- JSUTIL-59
Validate 'Attachment required'

- JSUTIL-67
Copy value now fails for single select to group picker combination - fixed

- JSUTIL-68
Catch NPE

- JSUTIL-70
Take 1 user from a collection of user to set a single value user field.

- JSUTIL-38

Exisitng comments on the issue are no more evaluated. Only the comment in the transition screen.

- JSUTIL-49

The workaround with a value like

[[GenericEntity:Component][id,10301][project,10000][description,null][name,Back End][lead,null][assigneetype,0][url,null]]

does not work anymore. Instead, you now can specify just the name of the component, like 'Back End'

- JSUTIL-55

* Support for Jira 4.4

* Setting project custom fields supported

* JSUTIL-27: Setting version custom fields supported

* JSUTIL-29: Setting cascading select custom fields supported

* JSUTIL-13: Reading Labels system field supported

JSUTIL-1

JSUTIL-10

JSUTIL-20

JSUTIL-33

JSUTIL-38