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:
- Carl E. Allen
(FOR JIRA SERVER/DC)
Important note: JMWE will NOT be changing or increasing prices in 2019, regardless of Atlassian and other vendor pricing strategies.