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

The primary goal of this version is to prepare for Atlassian's upcoming GDPR changes (currently scheduled for April 29, 2019). While it contains major changes, *it should be fully compatible with all your existing workflows*. If you identify what you believe is a regression, please report it to us as soon as possible through our [Help Desk](https://appfire.atlassian.net/servicedesk/customer/portal/11).

The upcoming GDPR changes will require that you **update your workflows** or they will eventually stop working. **See ****[Spring 2019 breaking changes for GDPR](https://appfire.atlassian.net/wiki/spaces/JMWEC/pages/466288912)**** for details**. 

This version of JMWE for Jira Cloud allows you to start updating your workflow *today* in preparation for Atlassian's breaking changes.

In addition, this version includes the following changes:

### Enhancement:

- <span style="color: #172b4d">A new button on the Nunjucks Editor toolbar allows you to look up and insert the accountId (the unique identifier that replaces the </span><span style="color: #172b4d">*username*</span><span style="color: #172b4d">) of a user into your template</span>
- <span style="color: #172b4d">The </span>`it`<span style="color: #172b4d"> variable is now available during Nunjucks Template testing in the Create Issue(s) post-function</span>
- <span style="color: #172b4d">The </span>`find`<span style="color: #172b4d"> and </span>`filter`<span style="color: #172b4d"> Nunjucks filters can now search for values deep inside an object (using field paths)</span>

### Bug fixes:

- The *Set field value of entity property* post-function was logging a spurious error when setting a non-existent property to an empty value (essentially deleting it)
- A recent Jira Cloud change made the Test Nunjucks Template dialog box disappear after clicking on the Issue Picker
- The *Unlink issues* post-function would fail when the condition did not filter the issues to unlink from