September 11, 2024

Created by Daniel Barrow
Last updated: Sept 16, 2024
2 min read

Feature Release - JMWE for Jira Cloud 1.2.33

Our team is thrilled to announce the latest release of JMWE for Jira Cloud. This release includes significant UI updates to several post functions as well as upgraded support for Forge Object fields in the Set issue fields post functions and increased audit data in Action administration pages.

Due to a recent bug, some Validators may behave inconsistently, especially when using the option Skip validation when cloning/creating an issue. Validators created after the release of version 1.2.32, or any Validators that are updated and saved after release, will not experience this particular issue.

If one of your Validators is not working as expected, after the update to 1.2.32 has been applied, simply open the Validator, make a small change and save it, then change it back. Any issues should be resolved. If issues persist, please contact Support and open a ticket.

 

Enhancements

Extensions

UI updates for various post functions

Several post function configuration screens have been updated with our new UI! Configuration options have been clarified and made more consistent. The following post function screens have been updated:

These changes are organizational and cosmetic only - no configurations options have been removed nor do you need to update any existing post functions!

‘Set issue fields’ post function support Forge Object fields

The Set issue fields post function has been updated to support Forge Object fields when selecting which fields to update using this post function. This update significantly enhances JMWE’s ability to set custom fields, including those created using 3rd party apps!

Bug fixes

The following bugs are fixed in this release:

  • ‘Copy field value’ incorrectly copies single picker field - In some configurations, the Copy field value post function incorrectly copies the value of a single picker field when using the option ‘Use value before transition’. This has been resolved.

  • ‘Copy subtasks to new issue’ option does not save - In some instances, the ‘Copy subtasks to new issue’ option was not saving correctly when creating or updating the Create issue(s) post function. This has been resolved.

  • Duplicate issue types displayed in ‘Create issue(s)’ configuration - The Create issue(s) post function page was sometimes displaying duplicate values in the Issue type configuration field. This has been fixed.

Â