December 16, 2024
Feature Release - JMWE for Jira Cloud 1.2.37
This release of JMWE for Jira Cloud includes a new post function - Log Work - and improved error capture for the Clear fields post function. Additionally, several UI updates have been made for the JMWE Administration pages and the Automation Rule Builder.
Enhancements
Extensions
New post function - Log Work
A new post function has been added to JMWE - Log Work! This post function can automatically add Worklog entries for calculated increments, including adjusting the issue’s estimate and adding scripted Descriptions!
‘Clear fields’ updated error logs
JMWE Logs have been enhanced to better capture when the Clear fields post function is configured to clear a field that is required (or cannot be empty). Now, when the post function attempts to clear a field that cannot be cleared, an Error will be added to the logs.
UI Updates
Actions and Extensions list in Administration pages
The administration pages for JMWE Workflow extensions, Shared actions, Scheduled actions, and Event-based actions have been updated for better usability. The Edit option has been removed from the Action menu ( ), and the Name value for all extensions or Actions are now clickable links; this enables you to easily open them in a new tab for editing without losing your location in the main list.
Automation Rule Builder extensions list
The Automation Rule Builder has been updated with options for better filtering as well as the option to Expand All and Collapse All tiles for the included post functions. The new options are located to the right of the Search field at the top of the post function list (pictured, right).
Bug fixes
The following bugs are fixed in this release:
Issue Resolved event does not trigger Event-based Action
In some configurations, the Issue Resolved event does not trigger Event-based Actions when the Action is configured to run for JSM projects. This has been resolved.
‘Field required’ validator incorrectly validates the Sprint field
The Field required validator is incorrectly returning valid results when checking the Sprint field. This has been resolved.
‘Field required’ validator incorrectly validates when checking a paragraph field
The Field required validator is incorrectly returning valid results when checking multiple fields that include Paragraph fields. This has been resolved.
‘Assign issue’ fails to assign the issue when run as ‘Current user’
Under some configurations, the Assign issue post function fails to correctly assign the issue. This has been resolved.
ParentIssue variable does not work when target issue is the current issue
The Nunjucks variable parentIssue fails to return a value when used in a Sub-task and the post function is configured to run against the ‘Current issue’ (the Sub-task). This has been fixed.
‘Transition issue’ post function incorrectly detects loops
In rare circumstances the Transition issue post function is incorrectly detecting loops and returning an error message. This has been fixed.
Shared Nunjucks templates incorrectly save with blank values
In some circumstances, the Shared Nunjucks templates could be saved with blank values for the name and Template fields. These fields now require values.
Description field in Automation Rule Builder disappears after editing
When editing an Action using the Automation Rule Builder, entering a blank space for the Description and then clicking away from the field causes the field to disappear from the screen. This has been resolved.
Need support? Create a request with our support team.
Copyright © 2005 - 2025 Appfire | All rights reserved.