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.
Jira Misc Workflow Extensions (JMWE) gives you the tools to automate virtually unlimited use cases no matter how simple or sophisticated they might be. It comes with many useful features, and most of them are covered in our new Getting Started Guide for JMWE for Jira Cloud.
Most videos in this guide - with an introduction by Rachel Wright, Certified Jira Administrator and author of the popular Jira Strategy Admin Workbook - are only a few minutes long. You can go through the entire guide in just one lunch hour!
Keep in mind that below each video, we include all steps covered in the example (for easy reference).
Jira automation is a no-code rule builder that lets users build "if-this-then-that" rules to automate their processes. The rules are triggered by Jira events and are relatively simple to build. Anyone with Global or Project Admin permissions can create automation rules to quickly automate many processes.
Automation is included with every Jira Cloud Standard, Premium, and Enterprise offering. However, there are notable Global and multi-project rule limits that may impact your experience with Jira's automation offering.
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."
Have you ever wanted to automate calculations based on data from your Jira fields? While Jira Cloud allows you to create custom fields, it doesn't provide a way to perform any calculations within those fields.
You can now use Event-based Actions, more specifically the feature's Issue Field Value Change trigger, to perform and automate calculations using values that appear in your Jira issue's custom fields.
