image
See how Jira and Innovalog's workflow automation can help
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
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
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.

DEC
16

Answer the Challenge to support a great cause!

Innovalog's Stump The Expert Challenge

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.

Continue reading
DEC
15

Jira workflow extension cheat sheets are here

Jira workflow extension cheat sheets are here
Continue reading
DEC
10

Automate on-the-fly calculations, such as work cost estimates, in less than an hour

guest-blog-post

Introduction (By Innovalog):

In your Jira projects, you might need to perform calculations based on data readily available in your Jira custom fields. While Jira gives you the ability to create custom fields, it doesn't give you the ability to perform calculations, even reasonably straightforward ones.

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
AUG
17

Everything you need to know about our pricing changes

JMWE and JMCF new pricing

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.

Continue reading
JUL
02

New features in Jira Misc Custom Fields (JMCF) now available

JMCF v 2.3.0 is here

JMCF v. 2.3.0 for Jira Server and Data Center is here, and it brings the following new features: 

Auto-indexing of related Jira issues makes searching accurate

​When displaying an issue, the value of all its Calculated (Scripted) fields is re-computed on-the-fly. Therefore, the value of any Calculated field will always be up-to-date. But when searching for issues, Jira uses the Jira index, which stores the value of all standard and custom fields and is only updated when an issue is modified (or the index is re-built).

Continue reading
JUL
02

Agile projects: prioritize what matters

Prioritize Jira Stories with Midori

Build a"low effort - high impact" Jira story report with the help of JMCF and Excel

All agile teams know the value of adaptive planning and quick response to change. While there are many tools and strategies that help you evaluate and prioritize - and reprioritize - your work, one you can always count on is "impact vs. effort."
Continue reading
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.

FEB
27

Jira Misc Custom Fields (JMCF) new version release

What's new in JMCF 2.2

JMCF v 2.2 is here! This version brings new features such as the new Transition Callers field type, support for Botron's Configuration Manager, and improvements that include better Duration field types, and more.

Continue reading
JAN
21

Verify approval in a Jira workflow

verify-approval-in-jira-workflow

It's smart to make Jira workflows as simple and flexible as possible. I like to give users multiple ways to transition issues between statuses and even let them skip statuses when needed. But sometimes skipping a status is undesirable or creates a compliance problem. Consider an approval status for example. You'd certainly fail an audit if work was started on an issue or an issue was completed before it was approved. Luckily, Innovalog's Jira Misc Workflow Extensions (JMWE) app has a validator to prevent it.

Use Case: Before work is started or an issue reaches its final workflow status, make sure it passes through the "Approval" status.

Bonus: Conditional Approval, to allow selected issues to bypass the "Approval" status.

DEC
04

New must-see features in JMWE 6.2 for Jira Server & Jira Data Center

What's new in JMWE 6.2 for Jira Server and Jira Data Center

The highly-anticipated Jira Misc Workflow Extensions (JMWE) 6.2 is here, and we are excited to let you know about a few important new features, as well as many improvements.

Continue reading
OCT
23

Want to migrate from JSU to JMWE?

Customers who run older Jira instances might still have the free version of JSU. Now it is no longer free and requires a license to operate, which you'd need upon upgrading to the latest Jira instance. Recently, JSU announced price increases, up to three-fold, and as of November 4, 2019, JMWE and JSU are priced the same*. However, some customers either consider purchasing a single workflow automation tool or want to replace JSU with JMWE. In most cases, thanks to many point-and-click extensions in JMWE, as well as extensibility via simple yet powerful scripting, it can be done easily.  

Continue reading
JUL
31

ScriptRunner vs JMWE: Choose the best app for your needs

jmwe-vs-scriptrunner
ScriptRunner for Jira and Jira Misc Workflow Extensions are the two top-selling apps in Admin tools and Workflow categories for Jira Server and Data Center, with 23K+ and 16K+ installations respectively (as of July 2019). 

Adaptavist's ScriptRunner provides sophisticated scripting options for many admin functions, while JMWE lets you quickly and easily configure and extend workflows - and only workflows. Many Jira Admins actually use both JMWE and ScriptRunner, but they use them for different things. 

Here, we outline the main differences between JMWE and ScriptRunner to help you decide when to use one app versus the other. 

JUN
11

Automatically transition Jira Issues

automatically-transition-rachel

As a Jira administrator, I frequently see this problem: child issues are closed but nobody remembered to close the parent issue. Users have already moved on to the next thing and the parent issue sits in its incorrect status forever. Or maybe it's the opposite: the Epic is closed, but its Stories, Bugs, and Tasks were forgotten.

When issue status does not reflect reality, reporting is a nightmare. All completed or unneeded issues should be transitioned to their final status. Why not take this step off your user's "to do" list and automate it? It's easy to automatically transition issues with Innovalog's Jira Misc Workflow Extensions (JMWE) app.

Use Case: When all child issues are closed, automatically transition the parent so users don't need to do it manually. Example: When all Sub-tasks are transitioned to the "Closed" status, automatically transition the Task issue to the "Closed" status.

Continue reading