Engineering Release 1.2.33 - JMWE for Jira Cloud
This release of JMWE for Jira Cloud includes several fixes for post functions, Actions (Shared, Event-based, and Scheduled) and migrations. Additionally, several display bugs have been resolved.
Contents |
---|
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.