June 18, 2024

Enable and disable individual post-functions within actions

Open

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.