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.
Contents |
---|
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
General responsiveness when editing or deleting Shared Nunjucks templates has been improved.
Status Pickers in extensions
When encountering missing status values, status pickers used in extension configuration screens (for example, Linked Issues Status Condition or Linked Issues Status Validator) displayed errors and showed all statuses as grey labels. Error handling has been improved and this has been resolved.
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.
Hotfix - JMWE for Jira Cloud
This release of JMWE for Jira Cloud includes hotfixes for performance and other issues. No UI changes will be visible to users/Jira administrators.
Contents |
---|
Bug fixes
The following bugs are fixed in this release:
Performance fixes for recent releases
Several performance-related issues occurring in recent releases have been resolved.
Unable to copy images to new issue
When using the /wiki/spaces/MWECS/pages/449708516 post function, images would fail to copy when included in the comment field after some special characters. This has been resolved.
Various UI fixes
The ‘Expand all/Close all’ option was missing from the /wiki/spaces/MWECS/pages/1126793316 configuration page. This has been fixed.
The /wiki/spaces/MWECS/pages/449708579 post function had several incorrect field labels. This has been fixed.
The User properties editor page displayed the list of properties too wide for the display, hiding the action buttons. This has been resolved.
Status picker validation errors
Missing Status values could cause any Status Picker (using in Validators, for example) to encounter errors. This has been resolved.
UI fixes for small viewports
The JMWE Rule Builder has been updated to better use vertical space when viewed on smaller viewports.
Migration errors display twice
When viewing a post function configuration post-migration, error messages are sometimes displayed twice. This has been resolved.
Missing icons in Nunjucks editor
In some circumstances, the Nunjucks editor would fail to load issue icons when testing a template. This has been resolved.
Deprecated post functions do not display configuration correctly after migration
When viewing deprecated post functions on the Post migration page, some configuration values do not display correctly and, therefore, cannot be resolved. This has been fixed.