Skip to end of banner
Go to start of banner

JSU 2.24.0 Release Notes

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

22st September 2020

The beecom team is happy to announce the release of JSU 2.24.0, which is now available on the Marketplace.

Improvements

  • "Update Any Issue Field" Estimate Fields (Original Estimate, Remaining Estimate, Timespent) now accept literal duration format (i.e. "1w 2d 3h"). For backwards compatibility, a numeric input value will be interpreted as a unit of seconds.
  • 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 Original Estimate, Remaining Estimate, and Timespent fields to the target issue/s.
  • If an error occurs while copying a custom field during a "JSU Bulk Copy" operation, the custom field which could not be copied is logged and the "JSU Bulk Copy" operation will continue copying issues.
  • When validating multiline text fields with regular expressions, the string is now split on the newline character before each line is tested against the expression.
  • Added a placeholder to all JQL expression texts to indicate that "key = '{issue.key}'" must be explicitly set to restrict results to only match the current issue.

Bugfixes

  • In some JIra/Service Desk version constellations, an error occurred while copying the Service Desk "Request Type" field in a "Create Linked Issue" post-function. The executing user context will still need project browse permissions to be able to successfully read the project request types (i.e. if the post-function is executed as an anonymous user, that user may not be able to resolve the list of available Request Types)
  • In some Jira/Service Desk version constellations, an error occurred while assigning the "Organization" field in a Update Any Issue" post-function on a "Create" transition when executed as an anonymous user. The executing user context will still need to be a member of the Organization or project administrator in order to be able to successfully read/write the "Organization" field.
  • The "watchers" system field was not copied in a "Create Linked Issue" post-function.

New Features

  • Added a "Status Change" workflow condition and precondition. These are useful in "From Any Status" workflow transitions, determining if a transition leads to another status or if the status remains unchanged.
  • No labels