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.

Designing and successfully implementing a business process is no small task. A great process aims to streamline tasks, ensure they are done correctly and promptly, and that all required information is recorded and made available to the right stakeholders during the right step of a workflow.

JMCF v. 2.3.0 for Jira Server and Data Center is here, and it brings the following new features: 

Auto-indexing of related Jira issues makes searching accurate​

​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).

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. 

This use case is for Jira Data Center and Jira Server. JMWE is also available in Jira Cloud, but it uses (optional) Nunjucks and Jira expressions to extend your workflows. 

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.

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 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.