Welcome!

Viewing time 2 min 49 sec  

 

Looking to build and automate Jira workflows?

You've come to the right place.

Jira Misc Workflow Extensions (JMWE) is an ALL-IN-ONE workflow automation app that powers millions of users worldwide, as well as half of all Fortune 100 companies. It's a top-rated and top-selling workflow app for Jira Cloud. Why? Because it gives you the tools to automate virtually unlimited use cases no matter how simple or sophisticated they might be.

 

What can you do with JMWE for Jira Cloud?

A lot! But here are just a few examples we cover in this guide to help you get started quickly:
  

 

Here is how JMWE helps you automate Jira Cloud:



Configure workflows - without code - using our 30+ post-functions, conditions & validators


Automate processes outside of workflows using Scheduled and Event-based Actions


Extend beyond limits with our powerful - yet simple to use - scripting engine

 

How to get started:

We welcome you to navigate this Getting Started Guide and cover it all in under 45 minutes! The videos will help you learn how to configure workflow extensions. You'll also discover how to use JMWE best. If you already have JMWE for Jira Cloud installed, great! If not, we encourage you to get the JMWE free trial so that you can configure a few automations in your own Jira Cloud instance. 
 


And just in case...

Here is how to access JMWE options in Jira:

 
JMWE configuration options are available to all Jira Admins in your Jira Cloud instance. 

TIP: If you are new to Jira and Jira workflows, explore these useful Atlassian resources first. 

 

10. JMWE vs. Jira Automation

Viewing time 2 min 16 sec

 

Limits on multi-project and global automation rule execution 
(in Jira Cloud Standard)

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. 

“As a Jira Cloud Standard admin, I was relying on the Automation allowances native to Jira Cloud - and quickly surpassed the 500 transactions / month, even though the team is very small and we have very few automations enabled. Increasing this would mean switching to Jira Cloud Premium, which is twice the cost of the app and all of our add-ons. JMWE is a much better value and has a lot more flexibility than Jira's automation - and you can save the native automation for smaller autos that won't be run as much.”
- Nicki Repici


Workflow Conditions and Validators to enforce processes

Since Jira Automation rules run outside of your workflows, there are NO Conditions and NO Validators that these automation features offer. JMWE offers several Conditions and Validators that can be easily configured, and more can be added using simple - yet powerful - scripting.


JMWE's Event-based Actions deliver additional advantages

  • With JMWE's Event-based Actions, you can automate actions using any of JMWE's post-functions, and since they are powered by our simplified scripting options, you can set up much more advanced rules… and we mean much more!
  • Built-in automation rules always run on behalf of the Automation "app user" - meaning their actions will appear under that Automation user, not an actual user. In JMWE's case, you have the option to run a rule on behalf of an actual user (such as the current user). 

“I can't recommend JMWE enough. Jira Automation is ok for relatively simple [tasks], but [JMWE] can handle an incredible level of complexity in comparison."
- Andrew Zietara




Check out this JMWE's Buyer's Guide [PDF]
. While it covers many of JMWE’s advantages, it will also help you understand native Jira automation features, as well as other types of automation apps.


 

1. Configuring Conditions


Jira workflow conditions control whether the transition should be visible to the user.  
If a condition fails, the user will not see the transition button on the 'View issue' page and will not be able to execute the transition. With JMWE, you can build many rules using our point-and-click conditions and even build your own.

 

Ensure that an epic cannot be closed until all its stories are closed.

Viewing time 3 min 39 sec


For your convenience, the steps from the above video have been outlined below.

 

An epic cannot be closed until all its stories are closed



  • In the Issue Link Type, select “is Epic of” (this means that the issue on which the condition will run is the Epic of the Stories that need to be checked).
  • Check off the DONE status (the status in which the linked issues must be for the transition to be enabled).



  • Add the condition, publish the workflow, and check your work. 

See it all in action in the video above.


 

Build-your-own Condition


JMWE comes with a diverse collection of point-and-click tools you can configure without code. However, with our build-your-own workflow conditions, validators, and post-functions - powered by our simple to use scripting editor and tester - you can build virtually unlimited use cases. For coding enthusiasts, the options are truly limitless.

No coding experience? No problem! See how easy it is to set up JMWE's "Build-your-own (scripted) Condition" without 'typing' a single line of code.

 

Enable the transition only for Medium priority issues.

Viewing time 49 sec  


For your convenience, the steps from the above video have been outlined below.

 

Enable the transition only for Medium priority issues. 

  • First, select the transition you want to add the condition to.
  • Choose the Build-your-own (scripted) condition and press Add.
  • In the “Select a field”, select “Priority”. Select a snippet issue.priority.name == "Blocker" and then change the priority from "Blocker" to "Medium".

  • You can test Jira expressions against any issue by pressing the “Test Jira expression” button.


  • If it works as expected (as above), add the condition, and you are all done. 

See it all in action in the video above.

 

4. Shared 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.

 

Add a comment on every transition to show when an issue was transitioned and by whom.

Viewing time 6 min 3 sec 



Why you need Shared Actions

  • Since Jira doesn't support 'copy-and-paste' of post functions, Shared Actions can help you reuse common configurations quicker and easier;
  • One Shared Action can include multiple post functions to run in sequence - you can create a more sophisticated process once, and then reuse it in your workflow transitions;
  • Using Shared Actions makes frequently used post functions easy to maintain - changes to the Shared Action will instantly apply to all transitions where it is being used.

For your convenience, the steps from the above video have been outlined below.

  

Add a comment on every transition when an issue was transitioned and by whom.

Instead of using a "Comment" post function added to each transition, add a "Shared Action" post-function instead. Configured once in the Shared Actions library, you'll always be able to modify it quickly - and it will apply to all transitions and workflows it is being used in.

  • Go to the Shared Actions library page accessible from the JMWE Apps page of Jira Administration.
  • Press "New shared action."
  • Give it an Action name: " Comment issue when transitioned," and press "Add post function."



  • Choose the "Comment issue" post function, and press "Add."
  • Add a Comment: "The issue was transitioned by," then expand the Editor and Tester, go to the "Global Variables" tab, and press on the currentUser | userInfo("displayName") button. It will add the code for the name of the current user right into the above comment field.



  • Press "Save" to add a post function.
  • Press "Save" to save the Shared Action.



  • Go to your workflow, and Edit it.
  • Select a transition to which to add the action. Go to the "Post Functions" tab and "Add post function."
  • Add "Shared Action (JMWE) app" post function to refer to the Shared Actions we set up previously.
  • Select our "Comment issue when transitioned" post function. Press Add.



  • Add this Shared Action to all your desired transitions. Publish your workflow, and check your work.



The benefit of Shared Actions - quickly modify your work

  • If you want to modify the comment that is posted automatically during these transitions, you edit your Shared Action, edit the post function in it, and change the comment body.

For example, add a date:

  • Add "on" by typing into the comment.
  • Go to the "Global Variables" tab and press now help option to insert into the comment field.



  • And Save.
  • Save the Shared Action - no need to modify or publish your workflows.
  • Check your work. Now the comment will include the date.

 

See it all in action in the video above.


Additional Tip:

In the Shared Actions page (see below), combine one or more JMWE post functions into an action. Then, use the Shared Action post function to add it to various transitions, even in different workflows.


Read the documentation