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.  

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.

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.

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.

​If you are contemplating attending Atlassian Summit 2020, consider this: you will spend a few knowledge-packed days amongst the most expert professionals, all available to you to ask questions, gather ideas, and explore future opportunities. Those professionals not only include the 'Atlassians' themselves, but also many super-knowledgeable consultants and trainers, such as our friend Rachel Wright. She is an entrepreneur, Certified JIRA Administrator, and author of the JIRA Strategy Admin Workbook.

Recently, Rachel published an article on how to convince your boss to send you to the event - get a few good ideas here.

Innovalog again is a proud sponsor of this mega event and we hope to see you in Las Vegas.

We are excited to announce several new features, plus many improvements, that will give Jira Admins considerably more options in configuring their workflows. Here is what's new in Jira Misc Workflow Extensions (JMWE) for Jira Server:

Hello software gurus!

We are expanding our development team and are now looking to fill these positions: Java Software Engineer and Full Stack Software Engineer. 

We are super-excited about our latest release of Jira Misc Workflow Extensions (JMWE) for Jira Cloud! It includes many new features that give our customers the ability to enhance automation by better customizing Jira workflows. Here is what's new in this release.

We know you have ideas on how to make your Jira workflows better, and we hope Jira Misc Workflow Extensions (JMWE) and Jira Misc Custom Fields (JMCF) help you do that.  Take a few minutes [updated 6/17/2019 - raffle closed] share how you use JMWE or JMCF and we'll share it with the world (we will respect anonymity if you prefer). Not sure how it would look? Just take a look at these real-life use cases already shared by other Jira superstars.

Join us in Las Vegas and see what's new with our products, get a one-on-one meeting with our CEO, and share your Jira experiences and feedback.

Viewing time under 60 seconds | Learn more about us

Going to the Atlassian Summit 2019? Come meet with the Innovalog team to see what's new with our products, to get a one-on-one meeting with our CEO, and to share your Jira experiences and feedback.

Recently, the Atlassian team has announced their new Top Vendor Program for the Marketplace Vendors. There is a total of three levels in the Top Vendor Program, which has replaced the previous Atlassian Verified program, with the two top distinct levels, Platinum and Gold, which are awarded based on annual sales. We at Innovalog are extremely excited to be recognized as one of 14 Platinum Top Vendors for 2018-2019.

We carry this recognition with pride and promise to uphold and surpass the required standards for support and quality of our products and for millions of users that run their processes powered by our workflow and productivity apps.

Several months ago, Shana Rusonis @Atlassian has published this great post and an infographic about the popularity of Jira, and shared some of the usage stats (PDF) from Jira's largest customers.

Here are some of the findings:

• Jira has sustained over 100,000 end users for one of Jira customers;
• It can support over 5,000,000 issues in a single instance, while the average number of issues for large customers is 1,400,000;
• On average, 400 workflows (and 900 custom fields) are used by Jira's largest customers.