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

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. 

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? 

 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. 

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).