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.
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.
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.
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?
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.
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.
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.
The major changes that Atlassian is making to the Jira REST API on top of which all apps are built, including JMWE for Jira Cloud, will impact some or all of your workflows. Though GDPR compliance was the primary reason for the changes, they will affect customers across all countries, not only those located in the European Union.
Starting on April 29th, in a continuous effort to improve customer trust and address all EU General Data Protection Regulation (GDPR) requirements, Atlassian is making very important changes to Jira Cloud that will affect (break!) some of your workflows. This affects all Jira Cloud customers.