image

Choose the best workflow app for your Jira automation needs

Jira Misc Workflow Extensions (JMWE) and JSU Automation Suite for Jira Workflows are designed for building and automating Jira workflows with a variety of extensions. Both offer several other features. There are, however, some differences between JMWE and JSU - this overview will help you choose the best option.


Want to read this comparison in a different format?   

HOW JMWE & JSU COMPARE


For Jira Server, Jira Data Center, and Jira Cloud
 

NO-CODE,
POINT-AND-CLICK TOOLS

Available in:



Both apps offer configurable point-and-click Conditions, Validators, and Post-functions
View the comparison table below


You can quickly configure workflows using point-and-click extensions without writing a single line of code. They are available right within Jira’s list of post-functions, conditions, and validators. Any Jira Admin can easily automate workflow functionality using these code-free tools.

POWERFUL
SCRIPTING TOOLS

Available in:



Only JMWE supports easy yet powerful scripting - a completely optional feature - on top of the point-and-click configuration.


When you need more sophisticated automation rules, quickly implement them using JMWE's simplified Groovy (in Jira Server/DC) or Nunjucks (in Jira Cloud) scripting. Its editor and tester - with built-in smart, interactive help - makes scripting easy, even for a novice. You can expand the editor with one click, right inside each extension.
 
 

Most, if not all, JSU workflow automations can be done with JMWE.
However, JMWE offers considerably more code-free extensions, including many essential ones.

 

 


Why have an option to extend with scripting?

So that you can automate almost anything.

JMWE gives you dozens of point-and-click tools. If you want more sophisticated scripting rules, JMWE makes it easy: post-functions, conditions, and validators can all be extended. ScriptRunner makes you write the whole script in detail; JSU has no scripting capabilities. With JMWE, you just customize with snippets of code, using Groovy in Jira Server/DC, or Nunjucks/Jira Expressions in Jira Cloud.

For example, if you want to transition all linked issues and provide, for one of the transition screen fields, a calculated value, you just need to write code to calculate the value (usually, a one-liner). With other scripting tools, you’d need at least 100 lines of code to give you the same functionality.

Better still, JMWE workflow configurations are easy to understand, so anyone who wants to re-use or edit them can do so without getting lost in lines and lines of code.

Our simplified API makes it super-easy to write scripts, and you won’t need to re-write or update them when the Jira API changes (Atlassian has a habit of making breaking changes to their Java APIs with every major release).

Learn more about workflow automation with JMWE scripting here:

FOR JIRA SERVER & DC       FOR JIRA CLOUD



“I consider JMWE to be the absolutely most necessary app for running our company. The secret? The completely optional Groovy editor - you start small, doing little things, and then eventually you're doing crazy stuff right in the workflows.”

- Carl E. Allen

 

Key Feature Comparison

Updated December 4th, 2019
 

WORKFLOW FEATURES

Point-and-click workflow extensions 

Here is an example of a JIRA SERVER/DC validator comparison 
39
extensions

FOR JIRA SERVER & DATA CENTER
25 post-functions  |  6 conditions  |  8 validators

30
extensions

FOR JIRA CLOUD
25 post-functions  |  3 conditions  |  2 validators
18
extensions

FOR JIRA SERVER & DATA CENTER
7 post-functions  |  5 conditions  |  6 validators

6
extensions

FOR JIRA CLOUD
6 post-functions  |  0 conditions  |  0 validators

Extend beyond point-and-click with scripting

JMWE's editor and tester makes scripting easy
 

FOR JIRA SERVER & DATA CENTER
Groovy scripting

FOR JIRA CLOUD
Nunjucks scripting
 

No scripting capabilities

Build-your-own (scripted) extensions

 

FOR JIRA SERVER & DATA CENTER
Scripted (Groovy) Post-functionCondition, and Validator

FOR JIRA CLOUDBuild-your-own Jira expression (scripted) Condition and Validator  
 
 

No scripting capabilities

Conditional execution

 

FOR JIRA SERVER/DC & JIRA CLOUD
(configurable options inside each extension)
 

FOR JIRA SERVER/DC ONLY
(through the use of separate pre-conditions)

JQL conditions

 

Through the use of a simple-to-use jqlSearch function

Transition trigger

Triggers transitions found by JQL query
 

In development, coming soon

Transition History Tab

See how it looks here
 

FOR JIRA SERVER/DC ONLY
Available in Jira Cloud only in older versions

OTHER FEATURES

Google Maps-based Custom fields

 

For calculated custom fields, take a look at
JMCF for Jira Server/DC
 

3 custom fields: Location Text, Location Select, Directions
FOR JIRA SERVER/DC ONLY

Bulk Copy of Issues

 
 

Requires Admin permissions in the target project
FOR JIRA SERVER/DC ONLY

Pricing

JMWE and JSU are the same price for:
Jira Server | Jira Data Center* 

For Jira Cloud:
$0.95 per user/mo (up to 100 users)
JMWE and JSU are the same price for:
Jira Server | Jira Data Center* 

For Jira Cloud:
$0.50 per user/mo (up to 100 users)

Where to get more information

 

*Except for the 50-user tier in Jira DC.
 
 

JMWE LETS YOU DO MORE

 
With JMWE, you can use many point-and-click, simple-to-configure extensions without any code. Plus, you can supercharge them further with powerful but simple scripting. It's easy to get started with out-of-the-box options, while gradually extending the use of scripting, giving you unlimited possibilities. Here are other reasons why you might prefer using JMWE:
 


PRICING DIFFERENCES:
NONE

(FOR JIRA SERVER/DC)


JMWE and JSU are the same price for Jira Server and Jira Data Center*
*As of Nov 5, 2019, after JSU's price increase, except for the 50-user tier in Jira DC

Important note: JMWE will NOT be changing or increasing prices in 2019, regardless of Atlassian and other vendor pricing strategies.


For Jira Cloud:
JSU is $0.50 per user/mo
JMWE is $0.95 per user/mo
(up to 100 users)



MANY KEY EXTENSIONS
ARE AVAILABLE
ONLY IN JMWE




OTHER IMPORTANT
FACTORS
TO CONSIDER


  • JMWE makes migration to Jira Cloud easier

    It provides almost the same list of extensions in Jira Cloud as in Jira Server and Data Center, which will be useful should you choose to switch in the future.
  • JMWE’s post-functions are simpler to deploy

    They include steps to configure conditional execution right within its configuration. JSU needs separate preconditions to be configured as a completely separate step in workflow configuration.
  • JMWE is an all-in-one app

    You get everything you need for automating workflows: configurable no-code tools AND an optional ability to extend further with scripting in more complex situations.
 
 
This comparison was prepared by Innovalog, the maker of Jira Misc Workflow Extensions. If you have any comments or find any inconsistencies, please write to jmwe [at] innovalog [dot] com.

JMWE on Atlassian MarketplaceJSU on Atlassian Marketplace