---
title: "January 27, 2025"
canonical: "https://support.appfire.com/space/JMWEC/3095889444/January%2027%2C%202025"
format: markdown
---
> Macro (aura-html)

# 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](https://appfire.atlassian.net/wiki/spaces/JMWEC/pages/1023803395) 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](https://appfire.atlassian.net/wiki/spaces/JMWEC/pages/465504849) post function fails to remove an existing value. This has been resolved.
- **‘Create issue’ post function incorrectly allows newline characters** - The [Create issue(s)](https://appfire.atlassian.net/wiki/spaces/JMWEC/pages/466256916) 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 ](https://appfire.atlassian.net/wiki/spaces/JMWEC/pages/465474211)post function copied the wrong comment. This has been resolved.
- **‘Copy issue fields’ doubles copied attachments** - In some configurations, the [Copy issue fields](https://appfire.atlassian.net/wiki/spaces/JMWEC/pages/466323304) 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](https://appfire.atlassian.net/wiki/spaces/JMWEC/pages/1023803395) 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](https://appfire.atlassian.net/wiki/spaces/JMWEC/pages/466321411) 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](https://appfire.atlassian.net/wiki/spaces/JMWEC/pages/466321741) 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](https://appfire.atlassian.net/wiki/spaces/JMWEC/pages/465474365) or [Validator](https://appfire.atlassian.net/wiki/spaces/JMWEC/pages/466226183), 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](https://appfire.atlassian.net/wiki/spaces/JMWEC/pages/465242701) 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.