Version 1.2.32 - Anticipated release date: Week of 22 July 2024

New features

Extensions

‘Assign issue’ post function

Similar to the Assign issue post function for JMWE for Jira Data Center, a new Cloud post function is planned for release that will allow for more general assignment of issues. This includes the previously unavailable option to migrate this post function from Jira Data Center to Jira Cloud.

‘Set issue security level’ post function

Another implementation of a JMWE for Jira Data Center post function, a new Cloud post function is being introduced that will enable you to set the security level for issues.

Actions

Copy extension to Shared Action

We’re adding a feature to all post function configuration screens that allows you to copy an entire post function to a Shared Action - new or existing - with a single click!

Enhancements

Extensions

UI updates for several post functions

A handful of post function configuration screens are getting a full makeover! This includes the Create issue(s), Email issue, Set issue fields, and Transition issue(s) post functions!

Actions

Better search for Projects and Issue Types

The Event-based Actions rule builder has been updated with better search when selecting Projects and Issue Types. For organizations with greater than 50 Projects or Issue Types, locating and selecting these will be quicker and more clear!

Bug fixes

The following bugs are fixed in this release:

• Execution errors do not open in new browser tab - In the Shared Action, Event-based Action, and Scheduled Action administration pages, clicking a link for an execution log does not currently open that log in a new browser window.

• Display issue with Execution time - In the Scheduled Action administration page, the execution time does not always display correctly depending on the number of issues that were affected by the action.

• Jira Expression editor experiences errors when adding code comments - Adding code comments in the Jira Expression editor after the executable code sometimes causes unexpected results in the extension execution.

• Search by Action ID returns inconsistent results - Searching by Action ID in the Shared Actions, Event-based Actions, and Scheduled Actions administration pages is sometimes returns inconsistent or incomplete results.

• ‘Return to previous status’ post function does not migrate - The ‘Return to previous status’ post function is not always migrating correctly when moving from Jira Server/Data Center to Jira Cloud.

Version 1.2.33-ENG - Anticipated Release Date: Early August, 2024

Bug fixes

The following bugs are planned for resolution in this release:

• Incorrect images copied when using the ‘Copy comments to related issues’ post function - Occassionally when using the Copy comments to related issues post function to copy comments that include images, the image that was last attached to an issue would get copied, instead of the image included in the comment being copied.

• Configurations not saved when switching between no-code and Jira expressions - In the Build-your-own (scripted) Condition and Build-your-own Validator, new configurations would sometimes fail to save when switching between the no-code and Jira expression versions of the extensions.

• Cloning an action results in post functions with identical ID values - In some instances, cloning an Action (Shared, Scheduled, or Event-based) would result in the included post functions having identical ID values to the original post functions - even when the two post functions have different configurations - resulting in confusing or broken error logs.

• Validations skipped incorrectly - In some instances, Validations are being skipped when the Skip validation when cloning/creating an issue option is checked, even when the triggering action is not cloning or creating an issue.

• Incorrect destination page when creating an extension - When using the Create new function from the JMWE workflow extensions administration page, switching the value of the Project pulldown menu would still result in opening the workflow for the first project selected.

• Broken links when testing Nunjucks Templates - In some instances, after testing a Nunjucks template, the links to more detailed information were broken and would return an HTTP error.

• JCMA migration of Event-based actions support for missing issue events - A few events were not being migrated successfully to JMWE Cloud when using Jira Cloud Migration Assistant (JCMA), including Issue Watcher Added and Issue Watcher Deleted. These events will now migrate to an “Issue Created” event in JMWE Cloud.

• Missing Shared conditions and Shared Validator migration warnings - Previously, um-migrated JMWE Shared conditions and Shared validators did not trigger warnings in the post-migration report if the warnings had been dismissed in previous migrations. These extensions will now trigger a warning in every post-migration report.

Version 1.2.33 - Anticipated Release Date: August 2024

Enhancements

Extensions

Set issue field(s) post function added support for Object field types

The Set issue fields post function will be updated to include support for Forge Object type fields.

Build-your-own (scripted) post functions now include ‘Run as’ configuration

The Build-your-own (scripted) post function will be updated to include a ‘Run as’ configuration, enabling the post function to run as a selected Jira user instead of only as the add-on user.

Linked Issues Condition & Validator support for min/max options

The JMWE Cloud versions of the Linked issues Condition and Validator will support configurations for minimum related issues and maximum related issues, similar to the Data Center versions.

New option to ignore fields on Clear Issue Fields post function

The Clear issue fields post function will be updated to ignore (not display) non-editable fields when selecting which fields to clear.

Post function editor displays transition information

The post function editor window will now include information about which transition the post function is currently applied. For administrators managing numerous post functions, you will now be able to tell which post function you’re editing at a glance!

User notifications added to post functions

Previous to this release, notifications for JMWE post function errors would only display in Jira if the logged in user is an Administrator. This update to several post functions will enable the option to display an error message to any user.

Actions

Action data includes user audit trail

Shared actions, Scheduled actions, and Event-based actions now include additional audit data on their management screens, including the user who last modified (or created) the action, when the last edit occurred, and when/who disabled or enabled the action last.