Blog from January, 2025

January 27, 2025

Engineering Release - 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:

  • New Issue Transition Experience breaks JMWE Validators - The new Jira Issue Transition Experience was causing JMWE Validators to fail. This has been resolved.

  • ‘Return to Previous Status’ not working - In some configurations, the Return to Previous Status failed to correctly transition issues; a new option has been added for “Return to previous distinct status” which will help guarantee issues are transitioned correctly.

  • ‘Set issue fields’ post function fails to remove Organization value - When configured to remove the value for the Organization field, the Set issue fields post function fails to remove an existing value. This has been resolved.

  • ‘Create issue’ post function incorrectly allows newline characters - The Create issue(s) post function was incorrectly allowing newline characters in the Summary field, causing the error message Incorrect request: {"summary":"The summary is invalid because it contains newline characters."}. This has been resolved.

  • ‘Copy comments’ post function copies incorrect comment - When there were more than 100 comments on the source issue, the Copy comments to related issues post function copied the wrong comment. This has been resolved.

  • ‘Copy issue fields’ doubles copied attachments - In some configurations, the Copy issue fields post function was doubling any copied attachments. This has been resolved.

  • ‘Return to Previous Status’ post function migration is missing errors - After migration using either JCMA or CMJ, the Return to Previous Status post function does not correctly display an error message detailing missing options. The post function on Data Center includes the option “Use a transition if one is available” where JMWE Cloud does not support this option; the migrated post function should display a warning about the missing option so that it can be corrected post-migration. This has been resolved.

  • Post functions using JQL search not triggering - Under some configurations, post functions using the option Issues returned by the following JQL Search to identify issues would not trigger correctly. This has been resolved.

  • JMWE Workflow Extension page showed empty workflows - In some circumstances, the JMWE Workflow Extensions administration page included workflows with no extensions in the Workflow pulldown menu; selecting a Workflow with no extensions caused the extensions list to never load or return an empty list. This has been resolved - empty Workflows should no longer be available from the pulldown.

  • The ‘Download logs’ button did not initiate a download - The JMWE Logs administration page includes a Download logs button, which did not always initiate a download but instead opened a new page with the logs in the requested format. This has been resolved.

  • Watchers field not correctly identified in Jira Expressions - There was a disconnect between JMWE referencing the Watchers field and what the Jira API returned, causing some Jira Expressions to fail, or fail to return results. This has been resolved.

  • ‘fieldHistory’ Nunjucks function returns null values for Asset fields - JSM Asset field values were not being returned correctly by the Nunjucks function fieldHistory(). This has been resolved.

  • Linked type “is Initiative of” not working - The Issue Hierarchy link type “is Initiative of” was not working when used in most post functions. This has been resolved.

  • Testing ‘Build-your-own’ Condition or Validator causes incorrect success message - When testing a No-code Build-your-own (scripted) Condition or Validator, a ‘Data successfully updated' message was incorrectly displayed (this did not affect the Condition or Validator and did not affect the testing result). This has been resolved.

  • Validator always fails with Asset and User fields - When using both a custom Asset field and a User Picker field, a Field Required Validator was always failing even when both fields were valid. This has been resolved.

  • Action menus don’t close after selecting an option - In some circumstances, the Action Menu did not close after selecting an option. This has been resolved.


January 14, 2025

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:

  • Copy Comment post function copies the wrong comment

    • The Copy comments to related issues post function was incorrectly copying the wrong comment when the source issue had more than 100 comments. This has been resolved.

  • Unable to open Shared Actions

    • Some users were encountering issues opening Shared Actions for editing; the page would display blank, followed by an error. This has been resolved.

  • Enable/Disable toggle for JMWE option

    • The JMWE Administration option that hides or shows the shortcut to JMWE in board and issue views was resetting. This has been resolved.

  • Errors in retrieving license information

    • Some users were experiencing an error when accessing JMWE administration pages or when editing or creating new extensions. This has been resolved.