See how Jira and Innovalog's workflow automation can help

New: Take your JMWE automation outside workflows (Jira Server/Data Center

Since the initial launch of Jira Misc Workflow Extensions back in 2008, we have regularly added features and functionality to make your management of Jira easier. As powerful as Jira workflows are, however, they aren't the only solution for every automation need, which is precisely the focus of our latest version, 7.0. Your Jira data center and server automation can now extend well beyond traditional workflows.

Here's what's new for data center and server:

Event-based Actions

Event-based Actions let you run any post function (or sequences of post functions) outside of status changes in Jira workflows using triggers including:

  • Issue Field Value Change
  • Issue Commented
  • Issue Updated
  • Issue Created & Issue Transitioned

These actions can keep issue fields synchronized, validate field changes, develop highly focused email notifications, and much more — all without service limits of Automation for Jira.

Scheduled Actions

Regular workflow post functions run on transitions, but with Scheduled Actions you can schedule post functions to run against issues returned by a JQL search.

This enables you to automate post-function execution at specific times on selected issues of your Jira instance, such as:

  • Send emails automatically every day
  • Create a new subtask every week
  • Update issue with information from another Jira instance every hour

Shared Actions

Rest assured, JMWE hasn't left Jira workflows behind by any means. In fact, the third major feature — Shared Actions — in this latest release is specific to workflows and is designed to ease your administrative burden.

Reusing and updating your workhorse post functions — or sequences of post functions — is now a simplified, standardized JMWE feature. Post functions can now be configured once and then added to multiple transitions across different workflows. You can quickly reuse common configurations, making them much easier to maintain across your Jira instance.


Reuse post-function configurations across your automation (Jira Server/Data Center)

 Once your Jira instance has multiple workflows, it's not long before you'll find yourself recreating the same post functions (and sequences of post functions) on numerous transitions and projects.

Now with JMWE on Jira server and Data Center, post functions — and post-function sequences — can be created once and reused across multiple workflows. Using the Shared Actions post function, you can create and more easily maintain a single source of truth for any of your commonly configured post functions.

For example, set multiple fields using set field value post functions and then add them to various 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.

And because they are post-function based, Shared Actions can also be used outside of Jira workflows with JMWE's Event-based Actions and Scheduled Actions.

How you benefit:Enter heading here...

  • Since Jira doesn't support copy-and-paste for 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 used.

How it works: 

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

 Use case: Add a comment to show who transitioned an issue and when


Schedule post functions to run at set times (Jira Server/Data Center)

Regular workflow post-functions run on transitions, but now you can schedule JMWE post-functions to run against issues returned by a JQL search. For example, you can automatically transition any issue escalated yet not addressed within your SLA threshold.

Things to know: 

  • ​Works based on predefined times, not workflow transitions
  • Flexible scheduling allows for any frequency (10-minute minimum)
  • Can execute many types of automations, such as workflow transitions, issue status and user changes, all in sequence
  • Can toggle on and off to update existing projects and make bulk changes (blog post)

How it works:

​In the Scheduled Actions library, set the schedule according to your requirements.  

Then, select your parameters for issues you'd like to target with this automation.

 Finally, create post-functions, for example, one to send a custom email, and another one to add a comment.

Use case: Send daily reminder email to assignees of issues that are "in progress" 


Event-based Actions bring Jira automation outside of workflow transitions (Jira Server/Data Center)

 Workflow post functions are a fantastic automation tool that enable Jira admins worldwide to move on from mundane, manual tasks and get to work that matters.

But when it comes to issue changes outside of a workflow transition — whether a field update, issue comment, etc. — the automation magic vanishes.

JMWE now offers Event-based Actions on Jira server and data center, extending the same post-function power from workflows to an abundance of issue changes, including:

  • Issue field value change
  • Issue commented
  • Issue updated
  • Issue created & issue transitioned
Here are three video use cases, using different post functions:

1. Synchronize issues: Keep subtask priority in line with changes to parent issue

2. Perform quick field calculations: Use existing field values to dynamically configure value of different field

3. Validate field changes: Check value of field calculation against requirements and show guided messages to users


New copy and set field value post functions accelerate your workflow building


Clunky Jira automation can be nearly as painful as manually solving a repetitive problem.

In that spirit, we recently released an update to Jira Misc Workflow Extensions for Jira Cloud that eliminates the need to use duplicate post functions to copy multiple field issues.

Now, a single post function, Copy issue fields, can be used to pass numerous field values from epics, issues or subtasks to any other issue fields you have.

Here's an example:

You want an issue's Assignee as the Approver of associated subtasks, while also ensuring a consistent Due date across the issue and its subtasks.

With the "Copy issue fields" post function, you simply map the issue to any related subtasks and connect Assignee to the Approver field within your Jira workflow. Do the same with the Due date fields and those field values will copy over as subtasks are created. 

Setting multiple field values 

Automation fields with pre-defined or calculated text or JSON values has long been a staple of JMWE through the "Set field value" post function. Now, however, you can set multiple field values within a single post function — no more building each in separate one-at-a-time processes. To highlight this multi-field functionality, we have renamed this post function "Set issue fields."

Some examples:

  • Text value: Add an epic's Reporter as a watcher of related user stories when a new story is created.
  • Calculated value: Set the Original Estimate field based on the difference between its creation and due dates.​

Also released this month, add the Comment Required Validator to your workflow transition to make it mandatory for the user to enter a comment while transitioning an issue. You can customize an error message to be displayed if the Comment field is left blank during the transition. You can also add conditional validation using Jira expressions to validate a transition for specific scenarios.


Maximize automation flexibility with Scheduled Actions on demand


Undoubtedly, there are ample automations that Jira administrators want to run at regular intervals. And that's why Jira Misc Workflow Extensions (JMWE) introduced Scheduled Actions last year, enabling Jira admins to run post functions using JQL queries.

But what about those one-off instances when you need to perform an action in Jira and possibly repeat it at irregular intervals? 

Continue reading

How to skip validation when cloning an issue

How to skip validation when cloning an issue

 This solution was provided by Joy Melendez. It has earned a $100 donation to FIRST

Troubleshooting challenge:

A JMWE validator is being used during the issue creation step. It validates that the issue has a certain linktype associated with it. The validator works properly when issues are being created. However, it doesn't work when a user clones an issue in Jira UI - even if the 'clone links' option is selected. 

Continue reading

Our new Getting Started Guide for JMWE for Jira Cloud is here!

Getting Started Guide for JMWE for Jira CLoud

Jira Misc Workflow Extensions (JMWE) gives you the tools to automate virtually unlimited use cases no matter how simple or sophisticated they might be. It comes with many useful features, and most of them are covered in our new Getting Started Guide for JMWE for Jira Cloud.

Most videos in this guide - with an introduction by Rachel Wright, Certified Jira Administrator and author of the popular Jira Strategy Admin Workbook - are only a few minutes long. You can go through the entire guide in just one lunch hour! 

Keep in mind that below each video, we include all steps covered in the example (for easy reference).

Continue reading

Jira Cloud Standard vs. Premium vs. Enterprise - what Jira's automation limits mean for you

Jira Standard vs Premium vs Enterprise

Jira automation is a no-code rule builder that lets users build "if-this-then-that" rules to automate their processes. The rules are triggered by Jira events and are relatively simple to build. Anyone with Global or Project Admin permissions can create automation rules to quickly automate many processes.

Automation is included with every Jira Cloud Standard, Premium, and Enterprise offering. However, there are notable Global and multi-project rule limits that may impact your experience with Jira's automation offering.

Continue reading

How to prevent a user from choosing an inapplicable support type

Prevent a user from choosing an inapplicable support type

 ​This solution was provided by Darryl Lee. It has earned a $100 donation to FIRST. Challenge was submitted by Rachel Wright.


A customer submits a support request through the Jira Service Management customer portal. A help desk technician receives the request and classifies it by choosing a Component representing an impacted software application or business area. They use a second field to select the type of support needed. 

The type of support available needs to be Component-specific. For example, if the Component is "email," the only applicable support selections are "troubleshooting" and "monitoring." If the Component is "network," the only suitable support selections are "monitoring" and "security."

Continue reading

Perform on-the-fly calculations with JMWE for Jira Cloud

Calculated Fields in Jira Cloud

Have you ever wanted to automate calculations based on data from your Jira fields? While Jira Cloud allows you to create custom fields, it doesn't provide a way to perform any calculations within those fields.

You can now use Event-based Actions, more specifically the feature's Issue Field Value Change trigger, to perform and automate calculations using values that appear in your Jira issue's custom fields.

Continue reading

JMWE Product Validation by Rodney Nissen / TheJiraGuy

JMWE Product Validation Report by TheJiraGuy

Jira Misc Workflow Extensions (JMWE) review by TheJiraGuy is now available. While an online review mostly covers JMWE features for Jira Cloud, this Product Validation Report [pdf] covers all platforms - Jira Cloud, Jira Data Center, and Jira Server.

According to Rodney, Jira workflow apps "all essentially do something similar, but each one's unique design makes it suited to a slightly different application or use case." Here, he takes "a more in-depth look at what Jira Misc Workflow Extensions (JMWE) by Innovalog is, what problems it solves, what makes it unique."

Did you know that JMWE holds a special place in Rodney's heart? Read the report to find out why

Continue reading

Introducing Event-based Actions for ultimate Jira automation

Ultimate Jira Automation - Event-based Actions

Automate processes outside of Jira Workflows with this new JMWE for Jira Cloud feature

If you've ever configured a Jira workflow, you know that regular workflow post-functions run on transitions - that is, when an issue transitions from one status to another. Let's say an issue transitions from OPEN to IN PROGRESS. As part of a workflow transition, many rules can be set up to automate processes.

Jira Misc Workflow Extensions (JMWE) for Jira Cloud includes dozens of configurable workflow post-functions that can enable a virtually unlimited number of use cases. However, what if important issue updates take place outside of status changes - without a transition taking place? That's where our new powerful Event-based Actions come in.

Continue reading

Set up a template to create multiple Jira issues

Create Multiple Jira Issues With JMWE

By Damian Rosochacki of Isos Technology

If you're a Jira admin or a power user, at some point, you've come across the following question, or a variant of it: "How can I create a template of issues?" Depending on the requirements, implementing a solution may take you anywhere from five minutes to a couple of days. Here, Damian from Isos Technology shows you how to quickly set up a template for an Epic, Issues, and Sub-tasks. It will take less than five minutes if you use the Jira Miscellaneous Workflow Extension app's Create Issue post-function.


How to require attachments, conditionally

Require attachments, conditionally - for Jira

​This solution was provided by Sait Kiremit. It has earned a $50 donation to FIRST by Blended Perspectives. 


​In Jira Service Desk, a customer request type needs either a custom field or an attachment. For example, if the user does not enter the value in the custom field called "Request Participants" on the request screen, the user will be warned of a required attachment. If the user enters the "Request Participants" field, this warning will disappear when creating a request.

Continue reading

Jira workflow extension cheat sheets are here

Jira workflow extension cheat sheets are here
Continue reading

A simple guide to choosing the right Jira workflow automation app


Designing and successfully implementing a business process is no small task. A great process aims to streamline tasks, ensure they are done correctly and promptly, and that all required information is recorded and made available to the right stakeholders during the right step of a workflow.

Continue reading

Jira Server End of Life: 10 things to know to make a better decision

9 things to know to make a better decision migrating from Jira Server

Since Atlassian has published the end-of-life timeline for Jira Server, we'd like to address a few points regarding features, pricing, and licensing related to our products. Hopefully, this can help you make confident decisions as you develop a plan for your team.  Please be aware that Jira Misc Workflow Extensions (JMWE) is available on all Jira instances; Jira Misc Custom Fields (JMCF) is available for Jira Data Center (DC) and Jira Server.

Continue reading

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.
Continue reading

What makes JMWE the #1 top-selling workflow app for Jira Cloud?

JMWE for Jira Cloud Demo
It can help you automate more of your workflows.

Jira Misc Workflow Extensions (JMWE) for Jira Cloud offers dozens of point-and-click workflow conditions, validators, and post-functions. You can easily configure them without any knowledge of scripting. 

But unlike other apps, JMWE also gives you additional configuration power through simplified scripting - this will come in handy when automating more sophisticated workflows. With our top-notch support and documentation, this flexibility earns JMWE the #1 top-selling workflow app spot for Jira Cloud.

In this 32-minute demo, Innovalog's founder David Fischer shows how JMWE can help you build better workflows. You can also navigate to any section - we list them below.
Continue reading