See how Jira and Innovalog's workflow automation can help
4 minutes reading time (799 words)

New features in JMWE for Jira Cloud

New JMWE for Jira Cloud features
We are excited to introduce new features in JMWE for Jira Cloud that have been deployed to your instance several days ago. We focus our app development on helping you easily automate your Jira workflows, and we hope this release will help you do that.

Take a look at the new features:

Many post-functions that were previously acting on the current issue can now act on specified target issues

​We have made ten of JMWE's post-functions more flexible by allowing you to specify the target issue(s). Options for the target issues include:

  • Current issue - this is the default option
  • Sub-tasks of the current issue
  • Parent issue of the current sub-task
  • Issues that belong to the current issue (Epic)
  • Epic of the current issue
  • Child issues of the current issue in the Portfolio hierarchy
  • Parent issue of the current issue in the Portfolio hierarchy
  • Issues linked to the current issue through any link type
  • Issues linked to the current issue through a specific link type
  • Issues returned by a Nunjucks template
  • Issues returned by a parameterized JQL search

These are the post-functions that now support specifying target issue(s):

Five post-functions are now deprecated in favor of better alternatives

Since the above post-functions are now more versatile, we have deprecated several post-functions that operate on Linked issues, such as the Clear fields of linked issues post-function. They are now marked as deprecated, and it is recommended to use their generic version (e.g., the Clear fields post-function) when adding a new post-function.

However, these deprecated post-functions will NOT be removed and will continue working, but they will not receive future enhancements that might be added to their generic counterparts.

The new Build-your-own post-function lets you do more with simplified scripting

You can build advanced workflows using Nunjucks, a sophisticated templating engine for JavaScript, and JMWE provides the tools to do just that (in addition to our point-and-click extensions).

The new Build-your-own (scripted) post-function allows you to run an arbitrary Nunjucks script. This can be used to make REST calls to external systems or to make calls to the Jira Cloud REST API.

The Build-your-own (scripted) post-function makes use of our proprietary, interactive editor and tester, which greatly simplifies scripting. It displays what the script should return, provides a description of global variables that are available to use in your scripts, gives an explanation of how to access any issue field, lists methods and properties available on issue objects, and more. 

You can click your way through scripting using the shortcuts provided, or use them for guidance and just write your own. With our intuitive editor & tester, and advanced documentation, you can quickly learn how to create sophisticated workflows, even with minimal coding experience.

You can also test your scripts against any issue to deploy your workflows bug-free.

Scheduled Actions for automating post-functions outside of workflows can now run on demand

As of April this year, you can schedule JMWE post-functions to run against issues returned by a JQL search with Scheduled Actions. You can set up many automation types, such as workflow transitions, issue status updates, and user changes, all based on your predefined schedules. However, you can now run any of your Scheduled Actions on demand with the new "run now" button to immediately run a scheduled action.

Tip: You can apply a one-time action to a set of issues, however, it can only run on up to 1000 issues at a time, and you'd need to set up a temporary schedule (i.e., to run once per year) to trigger the "run now" option.

Learn more about Scheduled Actions.

Other new feature and improvements

  • The Field required validator now supports the Time Spent field;
  • The Create Issue post-function now supports longer configurations;
  • The Copy Comments to Linked Issues post-function can now be used for bi-directional synchronization of comments - it won't create a ping-pong of comments between the two issues;
  • Build-your-own validators now have access to the original issue, i.e. the issue as it was before the user made changes on the transition screen, through the originalIssue variable;
  • Build-your-own conditions and validators now have access to the issue changelog.

Bug fixes and other improvements can be found in these release notes.

See new JMWE for Jira Cloud prices in effect on September 16th, 2020.

Innovalog has been acquired by Appfire
Everything you need to know about our pricing chan...

Related Posts



No comments made yet. Be the first to submit a comment
Wednesday, 05 October 2022

Captcha Image