This solution was provided by Joy Melendez. It has earned a $100 donation to FIRST.
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.
This solution was provided by Darryl Lee. It has earned a $100 donation to FIRST. Challenge was submitted by Rachel Wright.
A customer submits a support request through the Jira Service Management customer portal. A help desk technician receives the request and classifies it by choosing a Component representing an impacted software application or business area. They use a second field to select the type of support needed.
The type of support available needs to be Component-specific. For example, if the Component is "email," the only applicable support selections are "troubleshooting" and "monitoring." If the Component is "network," the only suitable support selections are "monitoring" and "security."
If you've ever configured a Jira workflow, you know that regular workflow post-functions run on transitions - that is, when an issue transitions from one status to another. Let's say an issue transitions from OPEN to IN PROGRESS. As part of a workflow transition, many rules can be set up to automate processes.
Jira Misc Workflow Extensions (JMWE) for Jira Cloud includes dozens of configurable workflow post-functions that can enable a virtually unlimited number of use cases. However, what if important issue updates take place outside of status changes - without a transition taking place? That's where our new powerful Event-based Actions come in.
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.
Read the original post: A Super Quick Way to Create Multiple Issues Using the JMWE Plugin
This solution was provided by Sait Kiremit. It has earned a $50 donation to FIRST by Blended Perspectives.
Challenge:
In Jira Service Desk, a customer request type needs either a custom field or an attachment. For example, if the user does not enter the value in the custom field called "Request Participants" on the request screen, the user will be warned of a required attachment. If the user enters the "Request Participants" field, this warning will disappear when creating a request.
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:
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.
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.
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.
Viewing time under 2 minutes | for Jira Misc Custom Fields
Here, we use the Transition Caller custom field type to display the person who resolved an issue (as an example). Using this custom field type, you can display, search for and report on the author of any transition based on actual transition IDs or between one, many, or all statuses. We cover the latter one in the above video.
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.
In Jira, you can customize your Board cards to help users focus on important details. You can filter according to your preferences, change colors, and display up to three fields. Adding a field you already have available in Jira is not difficult. However, you often want to show information not stored in an issue field, or pull it from a related issue.
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.
