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."
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.
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...
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:
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.
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.
Jira Software Server and Data Center 8.0 is built for speed and scalability. It brings substantial performance improvements and a more updated look and feel. Together with the new Jira Misc Workflow Extensions (JMWE) 6.0.0, you can make work flow better and faster than ever.
We are super-thrilled to announce the release of Jira Misc Custom Fields (JMCF) 2.0 for Jira Server. Over the past eighteen months, we've seen an increase of feature requests for our free JMCF app. With this commercial release, we tried to implement as many requested features as possible. This highly popular app has been truly transformed and we hope that it helps customers improve their day-to-day Jira processes.
We are excited to announce the new release of Jira Misc Workflow Extensions (JMWE) for Jira Server, which includes many new features. With a fully redesigned look and feel and brand new documentation, it is also much easier to use. You can build sophisticated workflows with the help of any of the 30+ workflow conditions, validators, and post-functions, or customize them with your own scripts using the brand new Groovy editor and tester.