How to calculate field values
While Jira allows you to create custom fields, it doesn’t provide a way to perform calculations within those fields. In this video, learn how to automate calculations using values that appear in your Jira issue’s custom fields using the Issue Field Value Change trigger of Event-based Actions.
Shared Actions let you create ‘shared’ JMWE post functions (or sequences of post functions) that can be reused in multiple workflow transitions. For example, set multiple fields using set field value post functions and then add them to transitions as one Shared Action, without the need to recreate them again and again. Or configure a post function to send an email, and then reuse it in different workflows.
Getting Started with JMWE for Jira Cloud
Explore this Getting Started Guide to learn how to configure many of the available Jira Misc Workflow Extensions features using specific examples.
By now, you already know that regular workflow post functions run on transitions – that is, when an issue transitions from one status to another (for example, an issue transitions from OPEN to IN PROGRESS). However, what if important issue updates occur outside of status changes – without a transition taking place?
While we’ve covered most of the JMWE features, this guide is only a starting point. If you haven’t done so yet, why not configure a few automations using JMWE? You can automate virtually any number of use cases, and you can make Jira work smarter for your organization.
JMWE vs. Jira Automation
Many different automations can be built using Jira’s native rules. However, as we mentioned in the above video, in multi-project and global automations, Jira Cloud Standard allows for a maximum of only 500 executions per month. This is a very small amount and can often be reached in hours, or even minutes. If your team exceeds this limit, automations simply stop running. With JMWE, you can run an unlimited number of workflow automation rules.
Scripting Editor & Tester
JMWE’s Editor and Tester is a very powerful tool. Its proprietary interactive inline help system 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.
Regular workflow post-functions run on transitions. However, with Scheduled Actions, you can schedule one or more JMWE post-functions to run against issues returned by a JQL search. For example, you can automatically transition any issue escalated yet not addressed for over 24 hours.
How to validate field changes
If important issue updates occur outside of status changes, you cannot validate field entries using workflow Validators. That’s where our powerful Event-based Actions come in. It offers a collection of triggers that will kick off one or more of JMWE’s post functions to automate processes outside of workflows. One of its triggers – Issue Field Value Change – will trigger an action when an issue field value changes.
Sequence of Post-functions
In Jira Cloud, during a transition, all post-functions run in parallel. Often, however, you need actions to be executed in sequential order. This post-function, Sequence of Post-functions, allows you to combine several JMWE post-functions into one sequence so that they can all run in a predefined order.