image
See how Jira and Innovalog's workflow automation can help
JUL
16

Maximize automation flexibility with Scheduled Actions on demand

1064x600_JMWE_Cloud_Scheduled_Actions_Hero-copy

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
Tags:
APR
19

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
APR
06

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
Tags:
MAR
09

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
Tags:
MAR
05

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.

Challenge:

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
Tags:
FEB
09

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
Tags:
FEB
01

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
JAN
27

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
JAN
25

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.

JAN
20

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. 

Challenge:

​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
DEC
15

Jira workflow extension cheat sheets are here

Jira workflow extension cheat sheets are here
Continue reading
DEC
07

A simple guide to choosing the right Jira workflow automation app

buyers-guide-jira-workflow-apps

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
NOV
09

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
SEP
08

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
JUL
29

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
Tags:
JUN
22

How to create Confluence pages from Jira issues - with links and data - in one click

jira-issue-confluence-how-to

Jira Misc Workflow Extensions (JMWE) comes with over 40 point-and-click Jira workflow post-functions, conditions, and validators (here is the PDF cheatsheet of all extensions). Configuring these no-code extensions will often be enough to automate most of your workflows, especially the essential ones. 

However, what sets JMWE apart from all the "code-free" Jira workflow apps is the extensibility of all these extensions with simplified scripting. Even if you are a Groovy novice, you can use code snippets right inside all extensions for more sophisticated workflows. Our user-friendly editor and tester will assist with scripting - often, you'll be able to click your way through "coding".

Additionally, advanced Groovy users can do super-powerful workflow automation with JMWE. Take a look at this use case that Carl E. Allen just shared on the Atlassian Community site

This use case is for Jira Data Center and Jira Server. JMWE is also available in Jira Cloud, but it uses (optional) Nunjucks and Jira expressions to extend your workflows. 

MAY
22

New JMWE for Jira Server and Data Center v6.3 is here

JMWE-version-6-3

We are excited to introduce a new version of JMWE for Jira Server and Data Center. It includes several significant new features, as well as many improvements. We hope that JMWE will help you automate more of your Jira workflows.  

Continue reading
APR
24

Workflow extension cheat sheet for Jira Server and Data Center

jira-server-workflow-cheat-sheet

 
Jira offers several built-in conditions, validators, and post functions that help you configure workflows. However, these native tools are often not enough for automating processes using workflows. Jira Misc Workflow Extensions (JMWE) and its 40+ point-and-click post-functions, conditions, and validators, you can quickly configure thousands of sophisticated use cases. You can find all these extensions right within Jira's list of post-functions, conditions, and validators.

Check out this cheat sheet, available at innovalog.com/cheatsheet, with all of the Jira & JMWE extensions available to you.

APR
07

Major new features released in JMWE for Jira Cloud

new-features-jira-cloud

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:

Continue reading
APR
07

Shared Actions: reusing post-function configurations [new in Jira Cloud]

shared-actions

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.

Continue reading