---
title: "JMWE for Jira Cloud 1.2.3-AC release notes"
canonical: "https://support.appfire.com/space/JMWEC/465474472/JMWE%20for%20Jira%20Cloud%201.2.3-AC%20release%20notes"
format: markdown
---
> Macro (aura-html)

This version brings major new features as well as many improvements:

# Highlights of this release:

##   
**<span style="color: #000000">Shared Actions: reusing post-function configurations</span>**

<span style="color: #000000">Post-functions (or sequences of post-functions) can now be configured once and then added to multiple transitions across different workflows. You can quickly reuse common configurations, and they are much easier to maintain. Here is how it works: in the </span><span style="color: #000000">[Shared Actions](https://appfire.atlassian.net/wiki/spaces/JMWEC/pages/466288975)</span><span style="color: #000000">, combine one or more JMWE post-functions into an action. Then,  use the </span><span style="color: #000000">[Shared Action post-function](https://appfire.atlassian.net/wiki/spaces/JMWEC/pages/466323396)</span><span style="color: #000000"> to add it to various transitions, even in different workflows. </span><span style="color: #000000">[Read this blog post to learn more](https://hub.appfire.com/popular-topics/workflow-and-automation/jira-misc-workflows-extensions-guide/#reusing-workflow-configurations)</span><span style="color: #000000">.</span>

## **<span style="color: #000000">Scheduled Actions: automating post-functions outside of workflows</span>**

<span style="color: #000000">Regular workflow post-functions run on transitions, but now you can schedule JMWE post-functions to run against issues returned by a JQL search. </span><span style="color: #000000">[Scheduled Actions](https://appfire.atlassian.net/wiki/spaces/JMWEC/pages/466321868)</span><span style="color: #000000"> offer flexibility: you can set up many types of automation, such as workflow transitions, issue status updates, user changes, all based on your predefined schedules. </span><span style="color: #000000">[Read this blog post to learn more.](https://hub.appfire.com/popular-topics/workflow-and-automation/jira-misc-workflows-extensions-guide/#scheduled-actions-for-jira)</span>

## **<span style="color: #000000">Sequence of Post-functions: ensuring a predictable post-function execution order</span>**

<span style="color: #000000">In Jira Cloud, during a transition, all post-functions run in parallel. This new post-function, </span><span style="color: #000000">[Sequence of Post-functions](https://appfire.atlassian.net/wiki/spaces/JMWEC/pages/466322933)</span><span style="color: #000000">, allows you to combine other JMWE post-functions into one sequence so that they can all run in a predefined order. The </span><span style="color: #000000">*Sequence of Post-functions*</span><span style="color: #000000"> guarantees the order of events, and replaces the need for using delayed execution. </span><span style="color: #000000">[Read this blog post to learn more.](https://hub.appfire.com/popular-topics/workflow-and-automation/jira-misc-workflows-extensions-guide/)</span>

## **<span style="color: #000000">Display Message to User: showing custom messages on transition</span>**

<span style="color: #000000">Use the new </span><span style="color: #000000">[Display Message to User post-function](https://appfire.atlassian.net/wiki/spaces/JMWEC/pages/465242070)</span><span style="color: #000000"> to show a custom message on the issue view page to the user triggering the transition. For example, during the transition that creates a new issue, provide the user with a link to the newly created issue. </span>

## **<span style="color: #000000">Easily access JMWE’s top features with one click </span>**

<span style="color: #000000">Jira Administrators can now navigate to the new Overview (a.k.a. Admin Console) page. If you already have the new navigation system, go to Jira Misc Workflow Extensions right from Jira's top Apps menu. Or you can quickly access the Overview page by simply typing </span><span style="color: #000000">*gg*</span><span style="color: #000000"> from any Jira page or by navigating to it through the Apps Admin section.</span>

  


---

# New features: 

- <span style="color: #000000">New libraries:</span>
  - [Shared Actions](https://appfire.atlassian.net/wiki/spaces/JMWEC/pages/466288975)
  - [Scheduled Actions](https://appfire.atlassian.net/wiki/spaces/JMWEC/pages/466321868)
- <span style="color: #000000">New post-functions:</span>
  - [Shared Action post-function](https://appfire.atlassian.net/wiki/spaces/JMWEC/pages/466323396)
  - [Sequence of Post-Functions](https://appfire.atlassian.net/wiki/spaces/JMWEC/pages/466322933)
  - [Display Message to User](https://appfire.atlassian.net/wiki/spaces/JMWEC/pages/465242070)

# Other new features and improvements

- <span style="color: #000000">New </span>`fieldHistory`<span style="color: #000000"> Nunjucks filter that returns the change history of a field</span>
- <span style="color: #000000">New </span>`previousStatus`<span style="color: #000000"> Nunjucks filter that returns the previous status of an issue, if any</span>
- <span style="color: #000000">A message (in the form of a "flag" at the top-right of the screen) is now displayed on the issue view when an error occurs during the execution of a post-function </span><span style="color: #000000">*and the current user is an admin*</span>
- <span style="color: #000000">The automatic issue view update feature at the end of a transition is now fully compatible with Jira Cloud's "new issue view"</span>
- <span style="color: #000000">Nunjucks templates and Jira expressions in transition conditions, validators and post functions tabs are now displayed using a full-featured code viewer</span>
- <span style="color: #000000">Group and project role membership can now be tested in Conditions and Validators (build-your-own, conditional validation, ...)</span>

# Bug fixes

- [[MWEC-472](https://appfire.atlassian.net/browse/MWEC-472)] - Transition History panel doesn't show all transitions if there are more than 100 field changes (Status or other) in issue history
- [[MWEC-473](https://appfire.atlassian.net/browse/MWEC-473)] - Assign to last role member post-function doesn't work if last matching role member is too far in the issue history
- [[MWEC-475](https://appfire.atlassian.net/browse/MWEC-475)] - Nunjucks Tester is broken in IE 11
- [[MWEC-476](https://appfire.atlassian.net/browse/MWEC-476)] - For some errors, the error is logged in Loggly but post function success is logged as well
- [[MWEC-478](https://appfire.atlassian.net/browse/MWEC-478)] - Field Required Validator configuration doesn't offer all eligible fields
- [[MWEC-479](https://appfire.atlassian.net/browse/MWEC-479)] - Setting the Sprint field to an empty value throws an error
- [[MWEC-480](https://appfire.atlassian.net/browse/MWEC-480)] - Error not logged when the Sprint field is set with a string
- [[MWEC-483](https://appfire.atlassian.net/browse/MWEC-483)] - Field Required Validator considers a numeric field with value 0 as EMPTY
- [[MWEC-486](https://appfire.atlassian.net/browse/MWEC-486)] - Nunjucks/Jira expressions help: examples for testing a field value are incorrect