Our team is thrilled to announce the latest release of JMWE for Jira Cloud 1.2.28.

Enhancements

Extensions

Updated UI for Build-your-own Condition and Build-your-own Validator

The Build-your-own Condition and Build-your-own Validator have been updated to include a No Code option for building Jira expressions! The new interface enables you to configure the Condition or Validator and JMWE will write the expression for you!

Create issue(s) post-function supports copying sub-tasks

The Create issue(s) post-function has been updated to include support for copying sub-tasks from the original issue (the issue that triggers the post-function) to the new issue(s). Please see the documentation for details on which fields are eligible to be copied.

Improved copying of attachments between issues

The Copy comments to related issues post-function has been updated with improved functionality for copying attachments. Now, when an attachment is copied, the post-function will check various file properties to determine duplicate files, and will append the file name of any file it determines is a duplicate.

Added support for ‘Team’ field in post-functions

Several post-functions have been expanded to include access to the Jira-native Teams field. The updated post-functions are:

• Clear fields

• Copy issue fields

• Create issue(s)

• Set issue field(s)

Validators updated with “Skip when cloning” option

It is now possible to configure JMWE validators to skip the validation when an issue is being cloned. All JMWE Validators have been updated to include this option.

Closed Sprints excluded from new issues and copied fields

When creating new issues or setting/copying issue fields, Sprint values for closed sprints will no longer be included when the post-function executes. When setting the Sprint field, if using a single value and that value is a closed sprint, the field will not be set; if using multiple values, the closed sprint will not be included in the set values. The updated post-functions are:

• Copy issue fields

• Create issue(s)

• Set issue fields

Actions

Updates to Shared Actions error logging

Shared Actions now log errors in the included post-functions even if the option Stop the action if a post-function encounters an error is not selected in the post-function configuration. A warning icon will be displayed in the post-function tile within the Shared Action, and a entry will be added to the JMWE Logs.

Scheduled Actions updated with ‘Run as user’ option

Scheduled Actions can now be configured to run as a specific user.

Migration

Updated support for “Remove values” in migrated Set issue fields

The post-function Set issue fields now includes enhanced support for migrating the option Remove values on multi-value fields. Migrations using JMCA and CMJ are supported!

Code Editors

Added support for Watchers and voters in Jira Expressions

Jira has added support for Votes/Voters and Watches/Watchers in Jira expressions; the Jira expression editor in JMWE has been updated to include access to these new fields.

Bug fixes

The following bugs are fixed in this release:

• JMWE Event-based Actions

  • JMWE Event-based actions were encountering issues access the new Parent field when configuring the event that triggers the action. This has been resolved.

• Shared Actions

  • The Shared Action editor was opening the Jira Workflow Editor in the same window/tab as the Shared Action editor which resulted in lost configurations. This has been fixed to open the Workflow Editor in a new tab.

• Automation Rule Builder

  • The Action Menu shortcut to copy an Action’s ID value was not copying the value to the clipboard. This has been fixed.

  • Minor display issues in the Automation Rule Builder have been resolved.

• Nunjucks template testing

  • In some instances when testing Nunjucks templates, the window for selecting an issue would display partially off-screen. This has been fixed.

• Link issues post-function

  • When editing an existing Link issue(s) post-function, the link type would revert to “blocks” any time the post-function was opened for editing. This has been fixed.

• Transition issue(s) post-function

  • When using the JMWE “Transition issue(s) post-function,” an error is thrown if the transition is performed by a user with no administrator privileges or project admin permissions and the post-function is configured to set a value on a field that doesn’t appear on the transition screen. This has been resolved.

• Copy issue fields

  • The Copy issue fields post-function was incorrectly logging changes to the current user even when the post-function was configured to run as the Add-on User. This has been resolved.

• Build-your-own Condition

  • In some instances the configuration would fail when Value to compare type was set to Text, even if the configuration was complete and valid. This has been resolved.

  • Display issues related to errors with required fields have been resolved.

• Linked Issues Validator

  • In some configurations, the Linked Issues Validator failed to correctly validate the configured Issue Type. This has been resolved.

• JCMA Migrations

  • Some migrations to Jira Cloud were encountering errors or incomplete migrations due to Comment issue(s) or Clear field(s) post-function configurations. These have been resolved.