November 25, 2024

Feature Release - JMWE for Jira Cloud 1.2.36

This release of JMWE for Jira Cloud includes various UI updates, including an expanded script editor window for longer scripts, an option to disable JMWE menus in various Jira views, and other Bug fixes.


Enhancements

Script editors

The script editors used throughout JMWE configuration pages have been updated to better use the available screen space. Editing longer scripts should now be more accessible.

JMWE Automation Rule Builder

The Automation Rule Builder has been updated to better display on small viewports. Administering your automations on the go just got easier!

Option to remove JMWE from menus

With an earlier release, shortcuts to the JMWE Administration pages were added to the project sidebar, the board menus, and the Action menu in the issue view. This update provides a toggle in the JMWE Configuration page that allows you to disable these additional menu options.

‘Copy issue fields’ post function UI fixes

The field labels in the Copy issue fields post function configuration screen have been updated for better clarity.

Bug fixes

The following bugs are fixed in this release:

  • Actions

    • For Event-based Actions, icons would sometimes fail to load on the configuration page. This has been resolved.

    • On the Scheduled Actions administration page, the Run Now option in the Action menu would not trigger a change to the UI, leading to some confusion on whether or not the action was initiated. This has been resolved.

  • Shared Nunjucks Templates

  • Status Pickers in extensions

  • Nunjucks parentIssue variable

    • In some circumstances, the parentIssue variable failed to retrieve values when executing a Nunjucks template. This has been resolved.

  • Post-functions

    • The Shared action post function configuration page had broken links and was missing tooltip text. These have been fixed.

  • User Properties Editor

    • There was a display issue on the User Properties Editor administration page that hid the Add button. This has been fixed.


Â