Bug fixes

The following bugs are fixed in this release:

• Cloning an Action results in duplicate IDs for included post functions

  • In some configurations, Actions (Shared, Event-Based, and Scheduled) will occasionally duplicate the ID of included post functions when the Action is duplicated (using the Clone function). This results in inconsistent log files and unexpected behaviors. This has been resolved and all cloned Actions now create new post functions with unique ID values.

• Clear Fields post function returns an error when encountering uneditable fields

  • The Clear Fields post function encounters an error and would terminate prematurely when it encountered uneditable fields (e.g. hidden fields or read-only fields). The post function has been updated to instead log an error (accessible through the JMWE Administration page) and then continue clearing all other fields when it encounters fields it cannot edit.

• Cannot save Build-your-own Condition or Build-your-own Validator when switching from No-code to Jira Expression

  • When editing an existing Build-your-own Condition or Build-your-own Validator and switching the type from No-code to Jira Expression, the extension cannot be saved because the Save button is disabled. This has been resolved.

• Set issue fields post function encounters an error when attempting to set more than one value for Organizations fields

  • The Set issue fields post function encounters an error when attempting to set the Organizations field using more than one value (using one value does not result in an error). This has been resolved.

• Set issue fields post function does not update and returns an error

  • In some configurations, the Set issue fields post function returns an error of 'You must select a valid field” when trying to update an existing post function. This has been resolved.

• Copy comments to related issues post function copies images incorrectly

  • When copying a comment that includes images, the Copy comments to related issues post function only copies the last image added to the source comment instead of copying all images added to the comment. This has been resolved.

• Create issue(s) post function returns an error when there are no linked issues

  • In some configurations, the Create issue(s) post function returns and error and fails to complete when the issue that triggers the post function does not have any linked issues. This has been resolved.

• Create issue(s) post function configuration screen does not display Issue Types

  • Occasionally the Create issue(s) configuration screen fails to display any Issue Types after selecting a Project. This has been resolved.

• Missing Shared Conditions and Shared Migrations were not always reported after migration

  • When migrating from Jira Server/Data Center, Shared Conditions and Shared Migrations would not always be reported as un-migrated when checking the post migration page. This has been resolved.

• ‘Sequence of Post-functions’ does not display all included post functions

  • In some circumstances, the post function Sequence of post-functions does not display all included post functions, or newly added post functions do not display correctly. This has been resolved.

• Transition issue(s) post function does not open

  • In some circumstances, the Transition issue(s) post function configuration screen fails to load when opening an existing post function. This has been resolved.

• Updated Actions do not show new configuration when re-opened

  • Occasionally, when saving an updated Action (Shared Action, Event-based Action, or Scheduled Action), the new configuration will not be displayed if that Action is reopened after saving. This has been resolved.

• Display issues in the script editor

  • The script editor in several updated post function configuration screens has a display issue when editing long scripts. This has been resolved.

  • In some extension configuration pages, the ‘Test Jira Expression’ button is displaying outside the editor window. This has been resolved.

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.

Enable and disable individual post-functions within actions

The JMWE Automation Rule Builder now includes options to disable post functions within an Action! You can now disable any individual post function from within the Action itself, enabling faster testing and troubleshooting, modified single runs, or temporary disabling of high volume post functions.

This update applies to:

• Shared Actions

• Scheduled Actions

• Event-based Actions

Improved filter and sort options

Each of the JMWE Administration pages for Actions has been updated to include better tools for filtering and sorting the list of respective Actions. In addition to searching by ID using the Search box, every column in the list of actions can now be sorted and filtered. Filter by the project where the action is used, the post-functions the actions contains, the Action’s execution status, and many more!

This update applies to:

• JMWE Workflow Extensions

• Shared Actions

• Scheduled Actions

• Event-based Actions

Extensions

‘Return to Previous Status’ post function

This release introduces a new post-function - Return to Previous Status. When triggered, this post-function will return an issue to the status it had before it’s current status (as long as there is a valid transition back to the previous status available). The new post-function increases parity between JMWE Data Center and JMWE Cloud, including migration support.

Other Enhancements

Custom domain support

JMWE Cloud is now supported when running Jira on custom domains.

Bug Fixes

The following bugs are fixed in this release:

• Actions (Shared, Scheduled, and Event-based)

  • The system was failing to list more than 50 results when searching for several types of items (e.g. Projects, Issues, Issue Types); in most cases the system failed to scroll enough, preventing the user from browsing all results. This has been resolved.

• Conditions and Validators

  • In some circumstances, the Conditional execution configuration was still being applied even after unchecking the option. This has been resolved.

• Scheduled Actions

  • When using the Search feature for JQL queries within a Scheduled Action, the preview would show results inconsistently. This has been resolved.

  • Resolved a display issue where values in the Schedule column of the list of Actions were being truncated.

• Event-based Actions

  • Resolved an issue with pagination in the list of Actions where using the page buttons at the bottom of the list would automatically reset to the first page.

  • Fixed a minor display issue for the Enabled column label.

• JMWE workflow extensions page

  • Clicking on Error or Warning badges in the Executions column did not open the Error logs page. This has been resolved and clicking the badges will now open that Administration page.

• Linked Issues Condition

  • JMWE Cloud was allowing blank characters in the Jira Expression field when selecting At least one linked issue must satisfy the condition below, which caused errors. This has been fixed.

• Linked Issues Status Validator

  • The Validator was incorrectly looking for all issue types to meet its criteria instead of only the selected issue types. This has been resolved.

• Nunjucks scripts

  • Setting the issue type to ‘Epic’ using a Nunjucks script would sometimes result in the error Incorrect request: {"parent":"data was not an object"}. This has been resolved.

• Migrations

  • Some migrated extensions were still showing errors in the Post Migration page even after those errors had been resolved. This has been fixed.

  • Some migrated Actions were displaying the error Groovy script must be converted into a Jira expression when their included post-functions did not include Groovy scripts. These should no longer display this error.

• ‘Run as’ user menu

  • The Run as user menu has been updated to correctly display users when first loading.

Enable and disable individual post-functions within actions

The JMWE Automation Rule Builder now includes options to disable post functions within an Action! You can now disable any individual post function from within the Action itself, enabling faster testing and troubleshooting, modified single runs, or temporary disabling of high volume post functions.

This update applies to:

• Shared Actions

• Scheduled Actions

• Event-based Actions

Improved filter and sort options

Each of the JMWE Administration pages for Actions has been updated to include better tools for filtering and sorting the list of respective Actions. In addition to searching by ID using the Search box, every column in the list of actions can now be sorted and filtered. Filter by the project where the action is used, the post-functions the actions contains, the Action’s execution status, and many more!

This update applies to:

• JMWE Workflow Extensions

• Shared Actions

• Scheduled Actions

• Event-based Actions

Extensions

‘Return to Previous Status’ post function

This release introduces a new post-function - Return to Previous Status. When triggered, this post-function will return an issue to the status it had before it’s current status (as long as there is a valid transition back to the previous status available). The new post-function increases parity between JMWE Data Center and JMWE Cloud, including migration support.

Other Enhancements

Custom domain support

JMWE Cloud is now supported when running Jira on custom domains.

Bug Fixes

The following bugs are fixed in this release:

• Actions (Shared, Scheduled, and Event-based)

  • The system was failing to list more than 50 results when searching for several types of items (e.g. Projects, Issues, Issue Types); in most cases the system failed to scroll enough, preventing the user from browsing all results. This has been resolved.

• Conditions and Validators

  • In some circumstances, the Conditional execution configuration was still being applied even after unchecking the option. This has been resolved.

• Scheduled Actions

  • When using the Search feature for JQL queries within a Scheduled Action, the preview would show results inconsistently. This has been resolved.

  • Resolved a display issue where values in the Schedule column of the list of Actions were being truncated.

• Event-based Actions

  • Resolved an issue with pagination in the list of Actions where using the page buttons at the bottom of the list would automatically reset to the first page.

  • Fixed a minor display issue for the Enabled column label.

• JMWE workflow extensions page

  • Clicking on Error or Warning badges in the Executions column did not open the Error logs page. This has been resolved and clicking the badges will now open that Administration page.

• Linked Issues Condition

  • JMWE Cloud was allowing blank characters in the Jira Expression field when selecting At least one linked issue must satisfy the condition below, which caused errors. This has been fixed.

• Linked Issues Status Validator

  • The Validator was incorrectly looking for all issue types to meet its criteria instead of only the selected issue types. This has been resolved.

• Nunjucks scripts

  • Setting the issue type to ‘Epic’ using a Nunjucks script would sometimes result in the error Incorrect request: {"parent":"data was not an object"}. This has been resolved.

• Migrations

  • Some migrated extensions were still showing errors in the Post Migration page even after those errors had been resolved. This has been fixed.

  • Some migrated Actions were displaying the error Groovy script must be converted into a Jira expression when their included post-functions did not include Groovy scripts. These should no longer display this error.

• ‘Run as’ user menu

  • The Run as user menu has been updated to correctly display users when first loading.

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.

Release date: 18 Jun 2024

Our team is excited to announce the latest release of JMWE for Jira Cloud 1.2.29.

Enhancements

Actions

Enable and disable individual post-functions within actions

The JMWE Automation Rule Builder now includes options to disable post-functions within an Action! You can now disable any individual post-function from within the Action itself, enabling faster testing and troubleshooting, modified single runs, or temporary disabling of high volume post-functions.

This update applies to:

• Shared Actions

• Scheduled Actions

• Event-based Actions

Improved filter and sort options

Each of the JMWE Administration pages for Actions has been updated to include better tools for filtering and sorting the list of respective Actions. In addition to searching by ID using the Search box, every column in the list of actions can now be sorted and filtered. Filter by the project where the action is used, the post-functions the actions contains, the Action’s execution status, and many more!

This update applies to:

• JMWE Workflow Extensions

• Shared Actions

• Scheduled Actions

• Event-based Actions

Extensions

'Return to Previous Status' post-function

This release introduces a new post-function - Return to Previous Status. When triggered, this post-function will return an issue to the status it had before it’s current status (as long as there is a valid transition back to the previous status available). The new post-function increases parity between JMWE Data Center and JMWE Cloud, including migration support.

Other Enhancements

Custom domain support

JMWE Cloud is now supported when running Jira on custom domains.

Bug fixes

The following bugs are fixed in this release:

• Actions (Shared, Scheduled, and Event-based)

  • The system was failing to list more than 50 results when searching for several types of items (e.g. Projects, Issues, Issue Types); in most cases the system failed to scroll enough, preventing the user from browsing all results. This has been resolved.

• Conditions and Validators

  • In some circumstances, the Conditional execution configuration was still being applied even after unchecking the option. This has been resolved.

• Scheduled Actions

  • When using the Search feature for JQL queries within a Scheduled Action, the preview would show results inconsistently. This has been resolved.

  • Resolved a display issue where values in the Schedule column of the list of Actions were being truncated.

• Event-based Actions

  • Resolved an issue with pagination in the list of Actions where using the page buttons at the bottom of the list would automatically reset to the first page.

  • Fixed a minor display issue for the Enabled column label.

• JMWE workflow extensions page

  • Clicking on Error or Warning badges in the Executions column did not open the Error logs page. This has been resolved and clicking the badges will now open that Administration page.

• Linked Issues Condition

  • JMWE Cloud was allowing blank characters in the Jira Expression field when selecting At least one linked issue must satisfy the condition below, which caused errors. This has been fixed.

• Linked Issues Status Validator

  • The Validator was incorrectly looking for all issue types to meet its criteria instead of only the selected issue types. This has been resolved.

• Nunjucks scripts

  • Setting the issue type to ‘Epic’ using a Nunjucks script would sometimes result in the error Incorrect request: {"parent":"data was not an object"}. This has been resolved.

• Migrations

  • Some migrated extensions were still showing errors in the Post Migration page even after those errors had been resolved. This has been fixed.

  • Some migrated Actions were displaying the error Groovy script must be converted into a Jira expression when their included post-functions did not include Groovy scripts. These should no longer display this error.

• ‘Run as’ user menu

  • The Run as user menu has been updated to correctly display users when first loading.

Release date: 01 Aug 2024

Our team is excited to announce the latest release of JMWE for Jira Cloud 1.2.32.

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.