Since their release last year, Event-based Actions have enabled thousands of Jira Misc Workflow Extensions (JMWE) Cloud customers to quickly create automations outside of workflow transitions.
With the latest update of JMWE Cloud, the Event-based Actions tool now has several new triggers that can connect with any post function:
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?
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).
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.
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."
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.
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.
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.
The upcoming holiday season will feel quite different for many people this year, which is why it's important that we give back. Give back to communities and groups who need extra support and love. Give back to people in need and to organizations that care for others.
Recently, I was chatting with Rodney Nissen (a.k.a, thejiraguy.com) about the Holidays, this challenging year, and, of course, Jira. An idea was born. An idea that evolved from a mere competition for a prize into a much bigger project - a charitable contest that will give back to the community.
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.
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.
First, on behalf of Innovalog, I would like to take this opportunity to thank all our customers for their business. This patronage truly matters to us, especially in these turbulent times. We strive to meet and exceed expectations whenever our customers need help, have a question, or reach out to our support team, and we are always committed to doing our best.
At Innovalog, we never increase our prices without first giving you valuable new functionality to automate more of your Jira processes. In the past 12-18 months, we have invested in a significant amount of new features and improvements, and we hope you find them helpful. This year, we have decided to make all pricing changes in one shot, on September 16th, 2020, as we have postponed some pricing changes from Spring to help organizations stabilize their business during this difficult time.
We are super excited to introduce new major features in JMWE for Jira Cloud. We hope this release will help make your job easier, and while we are making our product more feature-rich, we will not be raising prices. Now is not the time to burden your team and your company. Now is the time to help you better optimize your work and automate more of your Jira workflows.
Take a look at the new features now available in JMWE for Jira Cloud:
In Jira Cloud, during a transition, all post-functions run in parallel. Often, however, you need actions to be executed in sequential order. This new 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. For example, if you need, during a transition, to first create a new issue and then send a notification email mentioning the new issue, you need to make sure that the first post-function has finished running before starting the second one. The sequence would ensure that it runs properly.
Schedule actions for one or more JMWE post-functions to run against issues returned by a JQL search.
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 for over 24 hours.
Create shared JMWE post-functions (or sequences of post-functions) that can be reused in multiple workflow transitions.
In Jira Cloud, JMWE post-functions (or sequences of post-functions) can now be configured once and then added to multiple transitions across different workflows. It lets you quickly reuse (and then maintain) common configurations. 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.
