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.
JMCF v. 2.3.0 for Jira Server and Data Center is here, and it brings the following new features:
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).
Build a"low effort - high impact" Jira story report with the help of JMCF and ExcelAll 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."
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.
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.
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.
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.
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.
If you set up a Jira Service Desk email address, when a customer submits a support request by email, it is captured and becomes a new ticket (issue). These are added to your queues so that your team can focus on all your customer requests in one place. Sometimes, however, issues might not be relevant and you and you might consider it SPAM.
In the past, the issue view in Jira Cloud has displayed a transition tab, the feature some have come to rely on for activity information essential to their business processes. For example, managers and auditors could have a clear understanding of what actions have been taken on issues, that the right people work on or approve them, and that the processes always follow the appropriate workflow.
Since then, on the new issue view this tab is no longer available and only older Jira Cloud instances still show this option. However...
JMWE's new Transitions tab option gives users a precise view of transitions and if you are using this app, it is enabled by default. However, some older Jira Cloud instances might show a second "old view" Transitions tab. This is a legacy tab originally provided by Jira Suite Utilities (JSU).
To avoid confusing your users with two similar options, you might want to disable one of the tabs. But which one should you keep?
Here, we outline the main differences between JMWE and ScriptRunner to help you decide when to use one app versus the other.
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.