$customHeader
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

Space Index

0-9 ... 0 A ... 13 B ... 1 C ... 41 D ... 2 E ... 5
F ... 10 G ... 13 H ... 5 I ... 11 J ... 64 K ... 1
L ... 8 M ... 5 N ... 0 O ... 3 P ... 13 Q ... 0
R ... 9 S ... 29 T ... 12 U ... 10 V ... 5 W ... 6
X ... 0 Y ... 0 Z ... 0 !@#$ ... 0    

0-9

A

Page: Accessing the fields of an issue
This document details how to access the details of issue objects, such as the one provided by the issue, linkedIssue and parentIssue variables, as well as Issue objects returned by other methods such as getParentObject(), getEpic() or getLinkedIssues(). Y
Page: Add a certain number of days to a date excluding the weekends
Abstract This code snippet adds a certain number of days to a date excluding the weekends. By default, when you add a certain number of days to a date the weekends are included. To exclude them, you can use this snippet. Logic Fetch the number of days to
Page: Add a web link to an issue
This article provides the code snippet to add a web link to an issue, using Scripted (Groovy) operation on issue (JMWE app) https://innovalog.atlassian.net/wiki/spaces/JMWE/pages/139635057/Scripted+Groovy+operation+on+issue post-function. Instructions Nav
Page: Add certain number of minutes/hours/days/weeks/months to a date
Abstract This code snippet adds a certain number of minutes/hours/days/weeks/months to a Date/Date-Time picker field. Logic Add the number of minutes/hours/days/weeks/months to the date field using Use(TimeCategory http://docs.groovy-lang.org/latest/html/
Page: Add field value to parent
This post-function is deprecated. You should instead use the Copy field value to parent issue post-function together with the Add source value(s) to destination field option. A workflow post-function that adds the value(s) of a selected multi-valued field
Page: Advanced configuration and usage of the Create issue post-function
This document guides you on how to get more out of the Create issue post-function such as creating multiple issues one each based on the values of a multi-select field, linking newly created issues together, setting the field values of the newly created i
Page: API Interfaces
This section details the interfaces of the
Page: ApplicationUser interface
This document details the methods of the ApplicationUser https://developer.atlassian.com/static/javadoc/jira/reference/com/atlassian/jira/user/ApplicationUser.html interface you can use on any ApplicationUser, such as those returned by the Getters when yo
Page: Approval Interface
This document details the methods of the Approval interface you can use on an Approval returned by the Getters https://innovalog.atlassian.net/wiki/display/JMWE/Accessing+the+fields+of+an+issue when you access the Approvals field. Method Return type Retur
Page: Assign the related issues of the current issue to users in a Project role in Round Robin method
Abstract This code snippet assigns the related issues of the current issue to users of a project role in a round-robin method. Logic Access the users of a project role and run a loop on the related issues of the current issue to set the assignee of each r
Page: Assign to last role member
Are you using JMWE for Cloud and want to learn how to use this post-function? Head to our documentation here https://innovalog.atlassian.net/wiki/x/KoCcBQ. A workflow post-function that assigns the current issue to the last assignee who belongs to a selec
Page: Assign to role member
Are you using JMWE for Cloud and want to learn how to use this post-function? Head to our documentation here https://innovalog.atlassian.net/wiki/x/LICcBQ. A workflow post-function that assigns the current issue to the default member of a selected project
Page: Attachment Interface
This document details the methods of the Attachment https://developer.atlassian.com/static/javadoc/jira/reference/com/atlassian/jira/issue/attachment/Attachment.html interface you can use on an attachment of the issue returned by the Getters https://innov

B

Page: Basic Groovy Syntax
The syntax of the Groovy language is derived from Java, but is enhanced with specific constructs for Groovy, and allows certain simplifications. Groovy allows you to leave out some elements of syntax like package prefix, parentheses, and semicolon which b

C

Page: ChangeItemBean
This document details the methods of the ChangeItemBean https://docs.atlassian.com/DAC/javadoc/jira/reference/com/atlassian/jira/issue/history/ChangeItemBean.html interface you can use on any ChangeItemBean, such as those returned by the Getters https://i
Page: Checking the value of a multi-valued field
Abstract This code snippet checks the value of a standard or custom multi-valued type field (typically a multi-select field https://innovalog.atlassian.net/wiki/display/JMWEC/User+created+custom+fields). The multi-valued fields can either be a collection
Page: ChecklistItem interface
This document details the methods of the ChecklistItem interface you can use on any ChecklistItem, such as those returned by the Getters https://innovalog.atlassian.net/wiki/display/JMWE/Accessing+the+fields+of+an+issue when you access a Checklist field.
Page: Clear field value
Are you using JMWE for Cloud and want to learn how to use this post-function? Head to our documentation here https://innovalog.atlassian.net/wiki/x/LICcBQ. A workflow post-function that clears the value of the selected field(s) of the current issue. To ad
Page: Clear field value of linked issues
Are you using JMWE for Cloud and want to learn how to use this post-function? Head to our documentation here https://innovalog.atlassian.net/wiki/x/aQA2PQ. Documentation for is available here. A workflow post-function that clears the value of the selected
Page: Clear field value of related issues
Are you using JMWE for Cloud and want to learn how to use this post-function? Head to our documentation here https://innovalog.atlassian.net/wiki/x/aQA2PQ. Documentation for is available here. A workflow post-function that clears the value of the selected
Page: Closures
A closure in Groovy is an open, anonymous, block of code that can take arguments, return a value and be assigned to a variable. Groovy uses closures to specify a code to be executed each time and adds the extra methods ( each, any, every, find, findAll, c
Page: Cloud to Server migration challenges/limitations
This document lists the things to look out for when migrating JMWE configuration from Cloud to Server Challenges Workflows using JMWE post-functions/conditions/validators in the Cloud will break on the Server/Data Center because post-function configuratio
Page: Code snippet articles
These are the code snippet articles that can be used in Jira Misc Workflow Extensions Server.
Page: Code snippet to access a REST API and request JSON data
Abstract This code snippet is a specialization of the Code snippet to make an HTTP call and request data. It accesses a REST API, and thus requests JSON data and returns the parsed data through a Groovy script written in the Groovy editor of the add-on. L
Page: Code snippet to access the members of an Organization
Abstract This code snippet accesses the members of an Organization Logic Fetch the Organizations of the issue Fetch the users in these Organizations and return them Snippet import com.atlassian.servicedesk.api.organization.OrganizationService import com.a
Page: Code snippet to add a link to a workflow transition in the email
Abstract This code snippet adds a link to the specified transition in the email content of the email sent by the Email issue post-function Snippet <% import com.atlassian.sal.api.ApplicationProperties import com.atlassian.sal.api.UrlMode ApplicationProper
Page: Code snippet to check that the current user is a member of a specific group
Abstract This code snippet checks that the current user is the member of a specific group. Logic Iterate over the array of objects or set of values and check a specific field for the required value. Snippet ComponentAccessor.getGroupManager().isUserInGro
Page: Code snippet to fetch the current user's time zone
Abstract This code snippet fetches the current user's time zone. Logic Access the Time zone service of Jira and fetch the logged in user time zone Snippet import com.atlassian.jira.timezone.TimeZoneManager // access timeZone of current user def userTimeZo
Page: Code snippet to get the default value of a custom field
Abstract This code snippet gets the default value of a specific custom field. Logic Access the custom field by its name, get its relevant configuration for the current issue and then get its default value. Snippet import com.atlassian.jira.issue.CustomFie
Page: Code snippet to make a HTTP call from a Groovy script
Abstract This code snippet makes an HTTP call and processes the returned data. Logic Import the HTTPBuilder and the request methods. Make an HTTP by creating a new HTTP instance. Request the data passing the respective method, the content type, and the re
Page: Code snippet to send emails to members of group(s) selected in the multi-group picker field
This article provides the code snippet to send emails to users in the group(s) selected in a multi-group picker field in the Email issue (JMWE app) post-function. Instructions Navigate to the intended workflow to make the necessary changes in the edit mod
Page: Comment interface
This document details the methods of the Comment https://developer.atlassian.com/static/javadoc/jira/reference/com/atlassian/jira/issue/comments/Comment.html interface you can use on a Comment returned by the Getters https://innovalog.atlassian.net/wiki/d
Page: Comment issue
Are you using JMWE for Cloud and want to learn how to use this post-function? Head to our documentation here https://innovalog.atlassian.net/wiki/x/LoCcBQ. A workflow post-function that creates a comment on the current issue. The text of the comment can b
Page: Comment linked issues
Are you using JMWE for Cloud and want to learn how to use this post-function? Head to our documentation here https://innovalog.atlassian.net/wiki/x/MICcBQ. Documentation for is available here. A workflow post-function that creates a comment on all issues
Page: Comment related issues
Are you using JMWE for Cloud and want to learn how to use this post-function? Head to our documentation here https://innovalog.atlassian.net/wiki/x/MICcBQ. Documentation for is available here. A workflow post-function that creates a comment on all issue's
Page: Comment Required Validator
Are you using JMWE for Jira Cloud and want to learn how to use this validator? Head to our documentation here https://innovalog.atlassian.net/wiki/x/AQARlQ. A workflow validator that forces users to enter a comment during a transition. If the user does no
Page: Concatenate text fields without null - Groovy
Abstract This code snippet concatenates two text fields ignoring null values Logic Access the text fields and concatenate them Snippet textutils.noNull(<First text field>) + "<Delimiter>" + textutils.noNull(<Second text field>) Placeholders Placeholder De
Page: Conditional execution/validation using a Groovy expression
The Post functions and Validators provided by the JMWE add-on have a Conditional execution/Conditional Validation section to control the execution of the post-function/validator respectively. You need to provide a Groovy script in the editor based on whos
Page: Conditions
1 - Previous Status Condition A workflow condition that allows you to disable a particular transition (hiding it from the list of Available Workflow Actions) if the current Issue either: has never been in the specified Status or was not in the specified S
Page: Control structures in Groovy
To execute a block of code once or a multiple times based on a condition, you would need Control structures. Groovy supports the usual Conditional statements: if-else, "nested" if then else if, switch, try-catch-finally Looping statements: for, for in, w
Page: Copy field value from linked issues
Are you using JMWE for Cloud and want to learn how to use this post-function? Head to our documentation here https://innovalog.atlassian.net/wiki/x/MoCcBQ. Documentation for is available here. A workflow post-function that sets the value(s) of a selected
Page: Copy field value from parent issue
Are you using JMWE for Cloud and want to learn how to use this post-function? Head to our documentation here https://innovalog.atlassian.net/wiki/x/NICcBQ. A workflow post-function that sets the value(s) of a selected field with value(s) from the same fie
Page: Copy field value from related issues
Are you using JMWE for Cloud and want to learn how to use this post-function? Head to our documentation here https://innovalog.atlassian.net/wiki/x/MoCcBQ. Documentation for is available here. A workflow post-function that sets the value of a field to the
Page: Copy field value to linked issues
Are you using JMWE for Cloud and want to learn how to use this post-function? Head to our documentation here https://innovalog.atlassian.net/wiki/x/NoCcBQ. Documentation for is available here. A workflow post-function that copies the value(s) of a selecte
Page: Copy field value to parent issue
Are you using JMWE for Cloud and want to learn how to use this post-function? Head to our documentation here https://innovalog.atlassian.net/wiki/x/OICcBQ. A workflow post-function that copies the value(s) of a selected field to the same field of the issu
Page: Copy field value to related issues
Are you using JMWE for Cloud and want to learn how to use this post-function? Head to our documentation here https://innovalog.atlassian.net/wiki/x/NoCcBQ. Documentation for is available here. A workflow post-function that copies the value of a field to a
Page: Copy issue fields
Are you using JMWE for Cloud and want to learn how to use this post-function? Head to our documentation here https://innovalog.atlassian.net/wiki/x/AYA_jQ. A workflow post function that allows you to copy the values of one or more fields from the current
Page: Copy the attachments of the linked issues to the current issue
This document is obsolete. JMWE now supports copying of attachments across issues in the post-functions. Abstract This code snippet copies Attachments to the current issue from issues linked to it with a specific link type. Since currently copying and se
Page: Copy value from field to field
Are you using JMWE for Cloud and want to learn how to use this post-function? Head to our documentation here https://innovalog.atlassian.net/wiki/x/OoCcBQ. A workflow post-function that copies the value(s) of a selected field to another field of the same
Page: Copy worklogs from the current issue to the new issue in “Create / Clone issue(s) (JMWE app)” post-function.
This article explains how to copy work logs from the current issue to the new issue in Create / Clone issue(s) (JMWE app) https://innovalog.atlassian.net/wiki/spaces/JMWE/pages/139202100/Create+Clone+issue+s post-function. Instructions Navigate to the int
Page: Copying JIRA Standard fields from a linked issue during the Create transition doesn't work
This issue applies to JMWE 4.x only. If you haven't upgraded to JMWE 5, follow the workaround below. Problem Copying a Standard JIRA field from a linked issue (such as the Epic) fails on the Create transition. Details This is due to a limitation of JIRA.
Page: Create/Clone issue(s)
Are you using JMWE for Cloud and want to learn how to use this post-function? Head to our documentation here https://innovalog.atlassian.net/wiki/x/IoAzBw. A workflow post-function that create one or more new issue(s), optionally setting field values or c
Page: Current Status Condition
Are you using JMWE for Jira Cloud and want to learn how to use this condition? Head to our documentation here https://innovalog.atlassian.net/wiki/x/E4DANw. A workflow condition that allows you to hide/show a particular transition from the list of availab
Page: CustomerOrganization interface
This document details the methods of the CustomerOrganization interface you can use on an Organization field of a Service Desk issue, such as those returned by the Getters https://innovalog.atlassian.net/wiki/display/JMWE/Accessing+the+fields+of+an+issue
Page: Customizing further with Groovy scripts
Introduction to Groovy Groovy is an object-oriented programming language for the Java platform. It is a dynamic language with features similar to those of Python, Ruby, Perl, and Smalltalk. It can be used as a scripting language for the Java Platform. It

D

Page: Data types in Groovy
When you create a variable you reserve some space in memory to store the value associated with the variable. You may like to store information of various data types like string, character, wide character, integer, floating point, Boolean, etc. Based on th
Page: Display message to user
Are you using JMWE for Cloud and want to learn how to use this post-function? Head to our documentation here https://innovalog.atlassian.net/wiki/x/IoAzBw. A workflow post-function that displays a message to the user triggering the transaction, as a “flag

E

Page: Email Issue
Are you using JMWE for Cloud and want to learn how to use this post-function? Head to our documentation here https://innovalog.atlassian.net/wiki/x/aY9NC. A post-function that will send an email to certain recipients specified in the post-function configu
Page: Email templates
This document explains the different email templates that can be used in the Email issue post-function. Pick a template from the drop-down to use for the email. The HTML or raw text body will appear inside that template. On this page: Blank and Basic temp
Page: Event-based actions
JMWE’s Event-based actions enable administrators to run one or more post-functions independent of Jira Workflow transitions. You can create actions that run a sequence of post-functions every time an important change, such as the following, is made to an
Page: Execution logs
Execution logs are generated by every JMWE Extension (Conditions, Validators, and Post functions) when executed. These log files enable Jira administrators to monitor workflow extensions and provide detailed information about each execution at runtime. Th
Page: Expected value for each field type
When setting a field value, the post-function will fail to work as expected, if the input value does not match the expected field type. This document describes the format of values expected by a field when set using a post-function. The value can be a con

F

Page: Feature differences between JMWE Server/DC and Cloud
Feature differences between JMWE Server/DC and Cloud
Page: Fetch a subset of values of a multi-valued field based on a condition
Abstract This code snippet filters values from a collection of objects based on a condition Logic Iterate over the collection of objects and filter values that meet the condition Snippet //Define an array to find and store the filtered values def newValue
Page: Fetch the Component/s whose lead is a specific user
Abstract This code snippet fetches the Component/s whose lead is a specific user. Logic Access the available options for the issue's Component/s, find all Component/s whose lead is the specific user and return them. Snippet def components = issue.getAvai
Page: Fetch the current active sprint of a Scrum board
Abstract This code snippet fetches the current active sprint of a Scrum board. Logic Fetch the active sprints applicable to the current user and specified board and get the first sprint. Snippet import com.atlassian.greenhopper.service.rapid.view.RapidVie
Page: Fetch the value of a multi-value field when you know it has only one value
Abstract This code snippet retains the only value of a multi-valued type field which can either be an array of objects or a set of values. This snippet is useful when you know that the array has only one value and hence by applying the first or last metho
Page: Field has been modified Validator
A workflow validator that ensures that a certain field was modified during a transition. The selected field should be available on the transition screen for modification. To add 'Field has been modified Validator' to a transition: Click Edit for the work
Page: Field has single value Validator
A workflow validator which ensures that a multi-valued field does not contain more than one value during a transition. This validator can be customized such that field value(s) copied from the issue's sub-tasks can be excluded. To add 'Field has single v
Page: Field is required Validator
Are you using JMWE for Jira Cloud and want to learn how to use this validator? Head to our documentation here https://innovalog.atlassian.net/wiki/x/GQBJR. A workflow validator which ensures that the specified fields have a value during a transition. If a
Page: Find the earliest unreleased version scheduled after a certain date
Abstract This code snippet finds the earliest unreleased version scheduled after a certain date Logic Access the available versions for the issue and finds the earliest unreleased version scheduled after a certain date Snippet def version issue.getAvailab
Page: Find the next unreleased version
Abstract This code snippet fetches the next unreleased version available for the current issue Logic Access the available versions for the issue and filter the next unreleased version by the version date Snippet def version issue.getAvailableOptions("vers

G

Page: getAvailableOptions(String fieldNameOrID)
The getAvailableOptions(String fieldNameOrID) method on any Issue object, such as the one provided by the issue, linkedIssue and parentIssue variables (where applicable), as well as Issue objects returned by other methods such as getParentObject(), getEpi
Page: Getting started
image2022-6-14_11-27-40.png https://www.innovalog.com/products/jira-misc-workflow-extensions-server All-in-One app for Jira workflow automation "One of the best and most useful apps on the marketplace, especially if you have complex workflows." - Michael
Page: Getting the current user - Groovy
Abstract This code snippet fetches the user who triggered the current transition. Logic This snippet uses the currentUser built-in variable to fetch the ApplicationUser object representing the user who triggered the current transition. Snippet currentUse
Page: Groovy Console
This page allows you to run Groovy scripts against Jira issues without needing to edit a workflow transition. Navigate to the page using Jira Administration → Manage apps → Groovy Console. ezgif.com-gif-maker.gif Perform the following: Type: Select one of
Page: Groovy editor in JMWE
Starting with version 5.0.0, the JMWE add-on is provided with a Groovy script editor and tester in the post-function configuration screens. This document details the Groovy editor in JMWE, its features, its availability and keyboard shortcuts. On this pa
Page: Groovy examples
On creating a Bug set its Affects Version/s to the most recently released version Add the Set field value to constant or Groovy expression post-function to the Create transition of the Bug's workflow. Select the Affects Version/s field. Select Groovy expr
Page: Groovy expression input for fields
This document lists the expected result of a Groovy expression that should be provided to set Jira Standard and Custom fields. The easiest is to use the "Expected Value" tab of the Groovy editor help system. It lists the possible expected values for the s
Page: Groovy in JMWE
JMWE provides a wide array of easy to use workflow extensions to create advanced workflows. However, some advanced customization will require using scripting to further configure these extensions, such as: Auto-assign the issue to a user based on the requ
Page: Groovy script tester in JMWE
Starting with version 5.0.0, the JMWE add-on comes with a Groovy script editor and tester in the post-function configuration screens. This document details the Groovy script tester, its availability, and features. The Groovy script tester tool lets you te
Page: Groovy snippet to get the comment visibility
Abstract This code snippet checks the visibility of the comment added on the transition screen Logic Access the entity property which indicates the visibility of the comment. Snippet import groovy.json.JsonParserType import groovy.json.JsonSlurper def com
Page: Groovy templates
Groovy Template is a templating engine for JavaScript. It lets you insert dynamic content into any text through the use of templates. A template contains variables and/or expressions, which get replaced with values when a template is rendered. This is ver
Page: Groovy tutorial
Getting started This Tutorial introduces and familiarizes JMWE customers with writing Groovy code in JMWE workflow extensions (conditions, validators and post-functions) to automate their workflows to the next level. To write Groovy scripts in JMWE you do
Page: Group interface
This document details the methods of the Group https://developer.atlassian.com/static/javadoc/embedded-crowd-api/latest/reference/com/atlassian/crowd/embedded/api/Group.html interface you can use on a Group returned by the Getters https://innovalog.atlass

H

Page: Hide transition
A workflow condition that hides a transition from the user, thus preventing the user from triggering it. However, it remains available to scripts, remote API calls and post-functions like Transition current issue, Transition Parent issue etc. To add 'H
Page: How to copy remote links (Web Link) using Create / Clone Issue(s) Post-function
When using the Create / Clone Issue(s) Post-function https://innovalog.atlassian.net/wiki/spaces/JMWE/pages/139202100/Create+Clone+issue+s, there is no option to copy the remote links to the newly created issues. This article explains how you can copy ove
Page: How to receive email notification with issue details upon successful creation of issue
This article explains how to receive email notification with issue details upon successful creation of the issue using the Email Issue https://innovalog.atlassian.net/wiki/spaces/JMWE/pages/139896954post-function. After successful issue creation, send ema
Page: How to receive the last comment made on the issue in the email notification
This article explains how to receive the last comment made on the issue in the transition screen in the email notification using the Email Issue post-function. Use case: The last comment made on the issue should add while sending an email on a transition
Page: How-to articles

I

Page: Increase value of field
Are you using JMWE for Cloud and want to learn how to use this post-function? Head to our documentation here https://innovalog.atlassian.net/wiki/x/PICcBQ. A workflow post-function that increases the value of a selected numerical field by one. To add the
Page: Installation
Versions < 2.0 Install the plugin by copying the JAR to WEB-INF/lib inside your JIRA web application and restart JIRA. Version 2.0 and above Starting with version 2.0, the plugin is a "type TWO" plugin, which means that the plugin can be installed by copy
Page: Installation guide
This section guides you through the steps required to install the Jira Misc Workflow Extensions add-on on your Jira local server. To learn about the installation procedure see the following pages: Installing the add-on on your Jira server Post-Installati
Page: Installing the add-on on your Jira server
This section explains the installation of the add-on on your local Jira server. You must be a Jira administrator to carry out the instructions on this page. Installing within Jira (Recommended) It is recommended to install the Jira Misc Workflow Extension
Page: Introduction to Groovy
You can Skip this section if you are already familiar with the Groovy language and move on to the tutorials to start writing Groovy scripts in JMWE. This tutorial details the following chapters: References
Page: Issue Interface
This document details the methods you can use on any Issue object, such as the one provided by the issue, linkedIssue and parentIssue variables (where applicable), as well as Issue objects returned by other methods such as getParentObject(), getEpic() or
Page: issue.get("security") now returns a Long instead of a GenericValue
This page is obsolete! Problem After upgrading JIRA Misc Workflow Extensions to version 3.6.1 or JIRA Misc Custom Fields to version 1.6, scripts (in calculated custom fields or post-function execution conditions) that are using the following code will sto
Page: IssueLink interface
This document details the methods of the IssueLink https://developer.atlassian.com/static/javadoc/jira/reference/com/atlassian/jira/issue/link/IssueLink.html interface you can use on any issue link, such as those returned by the Getters https://innovalog.
Page: IssueLinkType interface
This document details the methods of the IssueLinkType https://developer.atlassian.com/static/javadoc/jira/reference/com/atlassian/jira/issue/link/IssueLinkType.html interface you can use on any issue link type, such as those returned by the Getters https
Page: IssueSecurityLevel interface
This document details the methods of the IssueSecurityLevel https://developer.atlassian.com/static/javadoc/jira/reference/com/atlassian/jira/issue/security/IssueSecurityLevel.html interface you can use on a Issue Security Level, such as those returned by
Page: IssueType interface
This document details the methods of the IssueType https://developer.atlassian.com/static/javadoc/jira/reference/com/atlassian/jira/issue/issuetype/IssueType.html interface you can use on any issue type, such as those returned by the Getters https://innov

J

Page: JIRA Misc Workflow Extensions 4.x Documentation
Please visit our Support Page http://innovalog.com/support/jmwe-for-jira-server for more information. This plugin provides a set of workflow extensions (conditions, validators and post-functions) that you can use to customize your JIRA workflows.
Home page: JIRA Misc Workflow Extensions for JIRA Server add-on documentation
This documentation applies to JMWE for Jira Server version 5.0 and above. Documentation for JMWE 4.x can be found here. This documentation is intended for the Jira Misc Workflow Extensions add-on for Jira Server and Data Center. If you are interested in J
Page: JMWE add-on specific tutorials
Welcome to the JMWE add-on specific tutorials which are practical guides using Groovy scripting for creating advanced workflows. This collection of tutorials show you how to accomplish certain functional use cases with Groovy scripts in the workflow exten
Page: JMWE administration pages
JMWE provides a new section of administrative tools. These can be accessed by following these steps: Log in to your JIRA Server instance as an administrator. Go to the Administration icon image2016-5-12 13:47:36.png and click on it. Locate Add-ons from th
Page: JMWE for JIRA Server 5.0.0 release notes
We are excited to announce JMWE 5.0, our biggest release ever! In this release, we've worked primarily on making JMWE much easier to use and configure. Highlights include: Completely redesigned configuration screens - it is now much easier to configure JM
Page: JMWE for JIRA Server 5.0.1 release notes
This version brings the following improvements: Enhancements: The "Field is Required" validator now supports the "Attachment" field Bug fixes: [JMWE-528 https://innovalog.atlassian.net/browse/JMWE-528] - Add field value(s) option of Copy Field Value From
Page: JMWE for JIRA Server 5.0.2 release notes
This version is a bug fix release only. Bug fixes: [JMWE-534 https://innovalog.atlassian.net/browse/JMWE-534] - Comment Issue and Comment Linked Issues post-functions throw an exception when the comment text is null [JMWE-536 https://innovalog.atlassian.n
Page: JMWE for JIRA Server 5.0.3 release notes
This version is a bug fix release only. Bug fix: [JMWE-548 https://innovalog.atlassian.net/browse/JMWE-548] - Post-functions that set a field during the Create transition make Clone operations fail
Page: JMWE for JIRA Server 5.0.4 release notes
This version is a bug fix release only. Bug fix: [JMWE-549 https://innovalog.atlassian.net/browse/JMWE-549] - Old-style workflow definitions cause NPE in most post-functions
Page: JMWE for JIRA Server 5.0.5 release notes
This version brings the following improvements: New Features: [JMWE-489 https://innovalog.atlassian.net/browse/JMWE-489] - New jqlSearch Groovy function for searching for issues using JQL [JMWE-564 https://innovalog.atlassian.net/browse/JMWE-564] - New ge
Page: JMWE for JIRA Server 5.0.6 release notes
This version is a bug fix release only. Bug fix: [JMWE-571 https://innovalog.atlassian.net/browse/JMWE-571] - Post-functions that operate on issue links cannot be created/edited without Jira Software running
Page: JMWE for JIRA Server 5.1.0 release notes
This version brings the following improvements: New Features: In Groovy scripts, you can now easily import (use) any Class or Component/Service exposed by Jira or any add-on installed in your Jira instance (JMWE-224 https://innovalog.atlassian.net/browse/
Page: JMWE for JIRA Server 5.1.1 release notes
New Features: [JMWE-597 https://innovalog.atlassian.net/browse/JMWE-597] - New originalIssue variable available to Groovy scripts [JMWE-598 https://innovalog.atlassian.net/browse/JMWE-598] - Issue.getFieldHistory method Bug fix: [JMWE-596 https://innovalo
Page: JMWE for JIRA Server 5.2.0 release notes
New Features: The Transition Issue, Transition Parent Issue and Transition Linked Issues post-functions now support passing values to the transition screen of the triggered transition The issue.get and issue.getAsString methods now support an optional sec
Page: JMWE for JIRA Server 5.2.1 release notes
Bug fix: [JMWE-618 https://innovalog.atlassian.net/browse/JMWE-618] - NullPointerException in Transition Parent Issue and Transition Linked Issues post-functions in certain cases
Page: JMWE for JIRA Server 5.5.0 release notes
We are excited to announce JMWE 5.5, which brings some major enhancements: Integrated help system In this release, we've worked primarily on making JMWE scripting much easier, through a brand new integrated online help system that includes: Expected value
Page: JMWE for JIRA Server 5.5.1 release notes
This version brings the following improvements: New Features: [JMWE-631 https://innovalog.atlassian.net/browse/JMWE-631] - New ApplicationUser.isInProjectRole Groovy method - useful in Conditions and Validators [JMWE-633 https://innovalog.atlassian.net/br
Page: JMWE for JIRA Server 5.5.2 release notes
This version fixed one compatibility issue: [JMWE-635 https://innovalog.atlassian.net/browse/JMWE-635] - Groovy tester incompatibility with certain other Jira add-ons
Page: JMWE for JIRA Server 5.5.3 release notes
This is a minor bug fix release that fixes the following issues: [JMWE-638 https://innovalog.atlassian.net/browse/JMWE-638] - New Statuses are not available in conditions and validators that depend on statuses [JMWE-639 https://innovalog.atlassian.net/bro
Page: JMWE for JIRA Server 5.5.4 release notes
This is a minor bug fix release that fixes the following issues: [JMWE-644 https://innovalog.atlassian.net/browse/JMWE-644] - More Help menu doesn't pop up [JMWE-645 https://innovalog.atlassian.net/browse/JMWE-645] - Groovy editor broken for new fields ad
Page: JMWE for JIRA Server 5.6.0 release notes
We are excited to announce JMWE 5.6.0, which brings the following improvements: New post-functions A Clear field value post-function to clear the value of one or more fields of the current issue A Clear field value of linked issues post-function to clear
Page: JMWE for JIRA Server 5.6.1 release notes
This version provides one enhancement and fixes one major bug: Bug fix [JMWE-671 https://innovalog.atlassian.net/browse/JMWE-671] Create issue Post Function: cannot save post-function with non-calculated field type Enhancement [JMWE-666 https://innovalog.
Page: JMWE for JIRA Server 5.6.2 release notes
This version fixes a bug that prevented configuring a Create/Clone Issue post-function with a sub-task issue type.
Page: JMWE for JIRA Server 5.7.0 release notes
We are excited to announce JMWE 5.7.0, which brings the following improvements: New workflow condition A Linked issue(s) Condition that checks issues linked to the current issue. Can be used to test the existence of certain issue links, or the details of
Page: JMWE for JIRA Server 5.7.1 release notes
This version provides a number of enhancements and bug fixes: New feature A new linkIssue() method on the Issue interface allows you to easily link issues from a Groovy script Enhancements The Transition Parent Issue post-function and the Transition Linke
Page: JMWE for JIRA Server 5.7.2 release notes
This version provides a number of enhancements and bug fixes: Enhancements The Attachment field can now be set Jira Portfolio's new Parent-Child Link type is now supported Bug fixes [JMWE-701 https://innovalog.atlassian.net/browse/JMWE-701] - Original Est
Page: JMWE for Jira Server 6.0.0 release notes
JMWE 6.0.0 brings the following improvements: Jira 8 compatibility JMWE 6.0.0 is fully compatible with Jira Software/Core 8, as well as with Jira Service Desk 4.0. JMWE 6.0.0 is also backward compatible with Jira 7.0.11 and above. Conditional validation J
Page: JMWE for JIRA Server 6.0.1 release notes
This version provides the following new feature and bug fixes: New feature New asUser() Groovy function to run some Groovy code as another user Bug fixes [JMWE-720 https://innovalog.atlassian.net/browse/JMWE-720] - Remove the obsolete Text option in the C
Page: JMWE for Jira Server 6.1.0 release notes
JMWE 6.1.0 brings the following improvements: New features The Status field can now be set directly in most post-functions (such as Create/Clone Issue(s), Set Field Value, etc.) The Issue Type field can now be changed, and the workflow of the issue will b
Page: JMWE for JIRA Server 6.1.1 release notes
This version reverts to the Groovy 2.4 platform to fix a conflict with other apps around the Groovy JSON parser (see JMWE-768 https://innovalog.atlassian.net/browse/JMWE-768).
Page: JMWE for JIRA Server 6.1.2 release notes
This version rolls back changes made in version 6.1.1 which would require a Jira restart to work. At this point, the Groovy JSON parser remains broken if you have installed another app that uses an older version of Groovy.​
Page: JMWE for JIRA Server 6.1.3 release notes
This version fixes one bug: [JMWE-753 https://innovalog.atlassian.net/browse/JMWE-753] - Cannot load FastStringService exception when using JsonSlurper
Page: JMWE for Jira Server 6.2.0 release notes
JMWE 6.2.0 brings the following improvements: New Transitions Activity Tab A new Transitions tab is now available under the Activity section of the issue view screen. It shows all past transitions, including, whenever possible, the name of the transition
Page: JMWE for JIRA Server 6.2.1 release notes
This version fixes the following bugs: [JMWE-819 https://innovalog.atlassian.net/browse/JMWE-819] - NullPointerException in JWME transition history panel after deleting a Status [JMWE-821 https://innovalog.atlassian.net/browse/JMWE-821] - Linked Issue Sta
Page: JMWE for JIRA Server 6.2.2 release notes
This version fixes the following bugs: [JMWE-817 https://innovalog.atlassian.net/browse/JMWE-817] - Syntax error in one Shared Groovy script shows on all other shared scripts [JMWE-823 https://innovalog.atlassian.net/browse/JMWE-823] - Related Issues Stat
Page: JMWE for JIRA Server 6.2.3 release notes
This version fixes the following bug: [JMWE-825 https://innovalog.atlassian.net/browse/JMWE-825] - NullPointerException in JWME transition history panel after deleting a workflow
Page: JMWE for JIRA Server 6.2.4 release notes
This version fixes the following bug: [JMWE-832 https://innovalog.atlassian.net/browse/JMWE-832] - Transitions tab: Exception thrown while trying to call getActions()
Page: JMWE for Jira Server 6.3.0 release notes
JMWE 6.3.0 brings the following new features and improvements: Send attachments using the Email Issue post-function The Email Issue post-function can now add issue attachments to the notification email. You can include all the attachments of the issue, on
Page: JMWE for JIRA Server 6.3.1 release notes
This version fixes the following bug: [JMWE-857 https://innovalog.atlassian.net/browse/JMWE-857] - JMWE 6.3.0 breaks the Jira issue navigator when Jira Software is not installed
Page: JMWE for JIRA Server 6.3.2 release notes
This version fixes the following bug: [JMWE-858 https://innovalog.atlassian.net/browse/JMWE-858] - JMWE 6.3.0 breaks existing Related Issues Status Conditions/Validators
Page: JMWE for JIRA Server 6.3.3 release notes
This version fixes the following bugs: [JMWE-860 https://innovalog.atlassian.net/browse/JMWE-860] - [Regression] cannot return GString as value for text custom field anymore [JMWE-861 https://innovalog.atlassian.net/browse/JMWE-861] - Red asterisk is show
Page: JMWE for JIRA Server 6.3.4 release notes
This version brings the following improvements and bug fixes: Improvements: Support for the Secure Fields app https://marketplace.atlassian.com/apps/1212681/secure-fields-data-security-privacy?hosting=server&tab=overview: when JMWE reads Secure Fields, it
Page: JMWE for JIRA Server 6.3.5 release notes
This version brings one improvement and one bug fix: Improvement: When copying a String (e.g. text field) to multi-valued field types whose values cannot contain a comma, the comma is considered as a value separator Bug fix: [JMWE-878 https://innovalog.at
Page: JMWE for Jira Server 6.4.0 release notes
JMWE 6.4.0 brings the following improvements and bug fixes: Improvements The Jira Service Management (formerly Jira Service Desk) request "channel" is now available from the Issue interface as the channel property The Organizations field of Jira Service M
Page: JMWE for Jira Server 6.5.0 release notes
JMWE 6.5.0 brings the following new features, improvements and bug fixes: New User Condition and Validator A new User Condition makes a transition available if the current user, the Reporter, the Assignee, or users in a field, belong to certain groups, pr
Page: JMWE for JIRA Server 6.6.0 release notes
This version brings the following changes: New features You can now copy from and to Insight custom fields, as well as set the value of Insight custom fields New getOrganization global function that returns a Jira Service Management Organization by name N
Page: JMWE for JIRA Server 6.6.1 release notes
This version fixes the following bug: JMWE-1000 https://innovalog.atlassian.net/browse/JMWE-1000 ClassCastException when using XmlSlurper in Groovy script
Page: JMWE for JIRA Server 7.0.0 release notes
This version brings several major features and improvements along with some bug fixes. New features Automate post-functions outside Jira workflows This release introduces the following powerful, new features that allow you to run post-functions independen
Page: JMWE for Jira Server 7.0.1 release notes
JMWE 7.0.1 brings the following improvements and bug fixes: Improvements Joda DateTime values are now supported as Date/Time values in addition to Java Date The "Run As" feature now supports running as the user in a field, or a user returned by a Groovy s
Page: JMWE for Jira Server 7.0.2 release notes
JMWE 7.0.2 brings the following improvements and bug fixes: Improvements Post-functions that copy values from a text field (or a text User Property) to a user picker field now recognize email addresses and even display names, not just usernames The Displa
Page: JMWE for JIRA Server 7.0.3 release notes
This version fixes the following bug: JMWE-1191 https://innovalog.atlassian.net/browse/JMWE-1191 Email Issue Post-function: Email is not sent in a few scenarios.
Page: JMWE for Jira Server 7.0.4 release notes
JMWE 7.0.4 brings the following improvements and bug fixes: Improvement In the field pickers, we are now adding the field ID next to the field name. This is a useful improvement, especially when more than one field with the same name exists. And bug fixes
Page: JMWE for JIRA Server 7.1.0 release notes
This version brings a major feature and an improvement along with some bug fixes. New feature Copy issue fields post-function Want to copy one or more fields either within the same issue or between issues? You can now use our Copy issue fields post-functi
Page: JMWE for JIRA Server 7.1.1 release notes
This version fixes the following bug: JMWE-1243 https://innovalog.atlassian.net/browse/JMWE-1243 Scheduled actions UI doesn't list its action if there is an action with a null name.
Page: JMWE for JIRA Server 7.1.2 release notes
This version fixes the following bug: JMWE-1263 https://innovalog.atlassian.net/browse/JMWE-1263 Fixed Scheduled Actions issue that was updating every issue even if all post-functions are skipped by their Conditional Execution JMWE-1281 https://innovalog.
Page: JMWE for JIRA Server 7.1.3 release notes
JMWE 7.1.3 brings the following improvement and bug fixes: Improvement JMWE-1311 https://innovalog.atlassian.net/browse/JMWE-1311 'Fields to monitor' drop-down field on 'Event-based action' editor page now supports all editable fields. And bug fixes JMWE-
Page: JMWE for JIRA Server 7.1.4 release notes
JMWE 7.1.4 brings the following: Security Improvements This version includes a security improvement (CVE-2022-0540 https://confluence.atlassian.com/jira/jira-security-advisory-2022-04-20-1115127899.html) This is a recommended update for all customers. Imp
Page: JMWE for JIRA Server 7.2.0 release notes
This version brings a major feature and improvements along with some bug fixes. New feature Migration support using Atlassian’s Jira Cloud Migration Assistant (JCMA) The JMWE app now has an automated migration path and can be migrated from Jira Server/Dat
Page: JMWE for JIRA Server 7.3.0 release notes
This version brings a major feature and improvements along with some bug fixes. New feature Duplicating Actions You can now create new Shared, Event-based and Scheduled actions by making a copy of an existing action. The Edit and Delete buttons next to ea
Page: JMWE for JIRA Server 7.3.1 release notes
This version, released on 20-JUL-2022, has the following changes: Improvements Improved compatibility with Jira 9 https://confluence.atlassian.com/jirasoftware/jira-software-9-0-x-release-notes-1142227613.html. Bug fixes
Page: JMWE for JIRA Server 7.3.2 release notes
This version has the following changes: Bug fixes
Page: JMWE for JIRA Server 7.3.3 release notes
JMWE 7.3.3 brings the following: Bug fix JMWE-1440 https://innovalog.atlassian.net/browse/JMWE-1440 Addressed Groovy Script execution issue
Page: JMWE for JIRA Server 8.0.0 release notes
This version, released on October 24th 2022, has the following changes: New feature Execution Logs To help fix any misconfigurations in Workflow Extensions, Executions Logs (Errors, Warnings, Successes) generated by JMWE can now be viewed from within Jira
Page: JQL expression editor and tester
This document describes the JQL expression editor and tester. It is available from the Link issues to current issue post-function and Target issues section of all post-functions that operate on related issues when Issues returned by a Groovy script or Iss

K

Page: Knowledge Base
Welcome to the knowledge base for the JIRA Misc Workflow Extensions (JMWE) for JIRA Server add-on. You will find within these pages How-to information and troubleshooting guides. You can find a lot of additional information from fellow users on Atlassian

L

Page: Label interface
This document details the methods of the Label https://developer.atlassian.com/static/javadoc/jira/reference/com/atlassian/jira/issue/label/Label.html interface you can use on any Label, such as those returned by the Getters https://innovalog.atlassian.ne
Page: Link epic of the current ticket to new ticket in “Create / Clone issue(s) (JMWE app)” post-function.
This article explains how to link the Epic of the current ticket to the new ticket in Create / Clone issue(s) (JMWE app) https://innovalog.atlassian.net/wiki/spaces/JMWE/pages/139202100/Create+Clone+issue+s post-function. Instructions Navigate to the inte
Page: Link issues to the current issue
Are you using JMWE for Cloud and want to learn how to use this post-function? Head to our documentation here https://innovalog.atlassian.net/wiki/x/XzlNC. A post-function that will link the current issue to all issues that satisfy a parameterized JQL quer
Page: Link parent of the current sub-task to new issue in “Create / Clone issue(s) (JMWE app)” post-function
This article explains how to link the parent of the current sub-task to the new issue in Create / Clone issue(s) (JMWE app) https://innovalog.atlassian.net/wiki/spaces/JMWE/pages/139202100/Create+Clone+issue+s post-function. Instructions Navigate to the
Page: Linked Issue(s) Validator
Are you using JMWE for Jira Cloud and want to learn how to use this validator? Head to our documentation here https://innovalog.atlassian.net/wiki/x/AQAUO. Documentation for JMWE is available here. A workflow validator which ensures that a link to one (o
Page: Linked Issues Condition
Documentation for is available here A workflow condition that allows you to hide/show a particular transition from the list of available transitions based on the issue's linked issues. The transition to which the condition is added will be available only
Page: Linked Issues Status Condition
Documentation for is available here. A workflow condition that allows you to hide/show a particular transition from the list of available transitions based on the status of the issue's linked issues. The transition to which the condition is added will be
Page: Linked Issues Status Validator
Are you using JMWE for Jira Cloud and want to learn how to use this validator? Head to our documentation here https://innovalog.atlassian.net/wiki/x/CoCPNw. Documentation for JMWE is available here. A workflow validator which ensures that the current iss

M

Page: Make external comment mandatory during a transition.
This article provides the code snippet that forces the user to add an external/public comment on the transition screen while executing a transition. Instructions Navigate to the intended workflow to make the necessary changes in the edit mode. Select the
Page: Make internal comment mandatory during a transition.
This article provides the code snippet that forces the user to add an internal comment on the transition screen while executing a transition. Instructions Navigate to the intended workflow to make the necessary changes in the edit mode. Select the requir
Page: Manipulating Data types
This section details the manipulations and operations on different data types in Groovy using methods of GDK and methods shared with JDK. On this page: Operations on Simple Data types Strings Some useful methods with examples are explained below. See her
Page: Migrating from Jira Cloud to Jira Server/Data Center
This article explains the steps required when migrating a Jira Cloud instance to Jira Server/Data Center when you were using JMWE workflow extensions on your JIRA Cloud instance. Background: Because of the way Atlassian's Connect framework is implemented
Page: Migrating to Jira Cloud using Jira Cloud Migration Assistant
The JMWE app has an automated migration path and can be migrated from Jira Server/Data Center (JMWE version 7.2.0 and later) using Jira Cloud Migration Assistant (JCMA) https://support.atlassian.com/migration/docs/jira-cloud-migration-assistant/ automatio

N

O

Page: ObjectBean interface (Insight)
This document details the methods of the Insight object https://insight-javadoc.riada.io/insight-javadoc-5.0/com/riadalabs/jira/plugins/insight/services/model/ObjectBean.html you can use to access and set the attribute values. denotes a method that is spe
Page: Operators in Groovy
Groovy supports all typical operators of Java, such as the Unary operators, Arithmetic operators, Assignment operators, Logical operators, Relational operators and Conditional operator. See below for examples using some of the operators. For more informat
Page: Option interface
This document details the methods of the Option https://developer.atlassian.com/static/javadoc/jira/reference/com/atlassian/jira/issue/customfields/option/Option.html interface you can use on any option, such as those returned by the Getters https://innov

P

Page: Parent Status Validator
A workflow validator which ensures that the current issue's parent is in one of the selected statuses. This is useful only for sub-tasks. To add 'Parent Status Validator' to a transition: Click Edit for the workflow that has the transition you wish to con
Page: Placing post-functions in a transition
The position of a post-function in the list of post-functions for a transition is an important factor for its proper execution. When adding a new post-function to a transition, you must move it to the appropriate position, which depends on the type of tra
Page: Post-functions
If you insert a Post-function in the Create transition, you must make sure that you place it: JIRA up to 6.4.x: after the Creates the issue originally built-in function. The exception is any post-function that writes to a system field, such as Set Field V
Page: Post-Installation
After you install the add-on, to verify that the installation was successful, follow these steps: Go to the Administration icon image2016-5-12 13:47:36.png and click on it. Locate Add-ons from the menu and click on it. Click on Manage Add-ons. Under the U
Page: Pre-defined custom fields
This page explains how to access the value of Pre-defined custom fields using Groovy. You can access them using the getters of the Issue interface. To understand how to write values into the writable custom fields see Raw value/text input for fields https
Page: Preparing your test environment
This page guides you through setting up a test Jira Server environment that you will be using throughout the rest of this tutorial. Before you begin To complete this tutorial you'll need the following: Jira Software application installed for your operati
Page: Prevent duplicate issue creation by the Create issue post-function
This article describes how to avoid the creation of a second issue by the Create issue(s) post-function when the same transition is triggered a second time. For example, if you are using a Create Issue(s) post-function on the "Escalate" transition of a su
Page: Previous Status Condition
A workflow condition that allows you to hide/show a particular transition from the list of available workflow actions, based on the previous status(es) of the issue. The transition on which the condition is configured will be available only if the issue
Page: Previous Status Validator
A workflow validator that makes sure the issue has been in a specified Status before. The user will be able to progress to the destination status of a transition, on which the validator is configured, only when the issue has previously been in the selecte
Page: Priority interface
This document details the methods of the Priority https://developer.atlassian.com/static/javadoc/jira/reference/com/atlassian/jira/issue/priority/Priority.html interface you can use on the priority of an issue, such as those returned by the Getters https:
Page: Program structure in Groovy
This section explains the program structure in Groovy. You can refer to the official documentation http://www.groovy-lang.org/structure.html of the Groovy language for more information. On this page: Packages A package is a group of similar types of class
Page: Project Interface
This document details the methods of the Project https://developer.atlassian.com/static/javadoc/jira/reference/com/atlassian/jira/project/Project.html interface you can use on a project, such as those returned by the Getters https://innovalog.atlassian.ne
Page: ProjectComponent interface
This document details the methods of the ProjectComponent https://developer.atlassian.com/static/javadoc/jira/reference/com/atlassian/jira/bc/project/component/ProjectComponent.html interface you can use on a Component, such as those returned by the Gette

Q

R

Page: Raw value/text input for fields
This document lists the expected text/raw input value that should be provided to set Jira Standard and Custom fields. The easiest is to use the "Expected Value" tab of the Groovy editor help system. It lists the possible expected values for the selected F
Page: Related Issues Condition
Are you using JMWE for Jira Cloud and want to learn how to use this condition? Head to our documentation here https://innovalog.atlassian.net/wiki/x/BYASO. Documentation for is available here. A workflow condition that allows you to hide/show a particula
Page: Related Issues Status Condition
Are you using JMWE for Jira Cloud and want to learn how to use this condition? Head to our documentation here https://innovalog.atlassian.net/wiki/x/EoBhNw. Documentation for is available here. A workflow condition that allows you to hide/show a particul
Page: Related Issues Status Validator
Are you using JMWE for Jira Cloud and want to learn how to use this validator? Head to our documentation here https://innovalog.atlassian.net/wiki/x/CoCPNw. Documentation for JMWE is available here. A workflow validator which ensures that the current iss
Page: Related Issues Validator
Are you using JMWE for Jira Cloud and want to learn how to use this validator? Head to our documentation here https://innovalog.atlassian.net/wiki/x/AQAUO. Documentation for JMWE is available here. A workflow validator which ensures that a link to one (o
Page: Release history
This page lists the release notes for every version of Jira Misc Workflow Extensions for Jira Server. Not using JMWE on Jira Server? If you are using JMWE on Jira Cloud, check out the JMWE for Jira Cloud Documentation instead. Release notes (from version
Page: RemoteIssueLink Interface
This document details the methods of the RemoteIssueLink https://docs.atlassian.com/jira/6.4/com/atlassian/jira/issue/link/RemoteIssueLink.html interface you can use on any remote link, such as those returned by the Getters https://innovalog.atlassian.net
Page: Resolution interface
This document details the methods of the Resolution interface you can use on a resolution, such as those returned by the Getters https://innovalog.atlassian.net/wiki/display/JMWE/Accessing+the+fields+of+an+issue when you access the Resolution field https:
Page: Return to Previous Status
A workflow post-function that returns the issue to its previous status. This is useful when multiple transitions can lead to the same status (e.g. Escalated) and you want to return the issue to the previous status. To add the 'Return to Previous Status' p

S

Page: Satisfaction interface
This document details the methods of the Satisfaction interface you can use on a satisfaction provided by a customer on a Service desk issue, such as those returned by the Getters https://innovalog.atlassian.net/wiki/display/JMWE/Accessing+the+fields+of+a
Page: Scheduled actions
Scheduled actions allow you to run one or more JMWE post-functions (in a sequence) at a specified time interval on the issues returned by a JQL search. You can use scheduled actions to: Send emails automatically every day. Transition an issue automaticall
Page: Scripted (Groovy) Condition
A workflow condition which hides/shows a transition based on the result of a Groovy expression. To add the 'Scripted (Groovy) Condition' to a transition: Click Edit for the workflow that has the transition you wish to configure the condition on. In the W
Page: Scripted (Groovy) operation on issue
A workflow post-function that executes a Groovy expression against the current issue. To add the 'Scripted (Groovy) operation on issue' to a transition: Click Edit for the workflow that has the transition you wish to configure the post-function on. In the
Page: Scripted (Groovy) Validator
A workflow validator that is based on the result of a Groovy expression. If the Groovy expression returns false, a validation error message will be displayed. To add 'Scripted (Groovy) Validator' to a transition: Click Edit for the workflow that has the t
Page: Select a subset of available options of a checklist/multi-select based on a regular expression - Groovy
Abstract This code snippet sets a Checklist/Multi-select type field with a subset of the available options based on a regular expression Logic Access the available options of the Checklist/Multi-select type field and retain all the options that match the
Page: Separation of Duties Condition
A workflow condition that enforces separation of duties (for SAS-70 https://innovalog.atlassian.net/browse/SAS-70 compliance), i.e. it makes sure that the same user cannot trigger two incompatible transitions on the same issue. To add 'Separation of Dutie
Page: Set a date field to today's date - Groovy
Abstract This code snippet sets a date field to today's date Logic Pass today's date Snippet new Date() Examples The output of this code snippet is a Timestamp http://docs.oracle.com/javase/7/docs/api/java/sql/Timestamp.html which you could use in: A Gr
Page: Set a single user picker field from the email address available in a free text field
It is possible to extract an email address from a free text field and then use that email address in a single user picker field. This article provides the code snippet to accomplish this using the Set field value https://innovalog.atlassian.net/wiki/space
Page: Set a version field to versions of all its linked issues
Abstract This code snippet sets a version field to versions of all its linked issues Logic Access the linked issues of the current issue, fetch the versions of each linked issue and return them. Snippet Set versions = [] issue.getLinkedIssues().each(){ ve
Page: Set an Estimate of the issue to the difference of two specific dates - Groovy
Abstract This code snippet sets an Estimate field to the difference of two specific dates of the issue. Logic Access the date fields of the issue and return their difference Snippet if(<Date object>) { return <Date Object> - <Second Date object> + "d" }
Page: Set assignee of the issue based on day of the month.
This article provides the code snippet to assign the issue to a user, based on the day of the month, using Set field value (JMWE app) https://innovalog.atlassian.net/wiki/spaces/JMWE/pages/68878480 post-function. Instructions Navigate to the intended work
Page: Set Component/s field from a Cascading field
Abstract This code snippet sets the Component/s field from the value of a Cascading field. This is useful if you have a large number of Components that can be organized in categories, and want to make it easier for users to find the appropriate Component
Page: Set field value
Are you using JMWE for Cloud and want to learn how to use this post-function? Head to our documentation here https://innovalog.atlassian.net/wiki/x/RoCcBQ. A workflow post-function that sets the value(s) of a selected field of the current issue. The value
Page: Set field value from User Property value
A workflow post-function that sets the value of a selected field of the current issue to the value of a User Property of the current user or the user in an issue field To add the 'Set field value from User Property value' post-function to a transition : C
Page: Set field value of linked issues
Documentation for is available here. A workflow post-function that sets the value(s) of a selected field of all issues linked to the current issue through a selected link type. The value can be either a constant, optionally including a Groovy template mar
Page: Set field value of related issues
Are you using JMWE for Cloud and want to learn how to use this post-function? Head to our documentation here https://innovalog.atlassian.net/wiki/x/SICcBQ. Documentation for is available here. A workflow post-function that sets the value(s) of a selected
Page: Set issue security level based on user's project role
A workflow post-function that sets the Security Level of the current issue based on the project role to which the current user belongs. To add the 'Set issue security level based on user's project role' post-function to a transition : Click Edit for the w
Page: Set issue, user or project Entity Property value
A workflow post-function that sets the value of a user, issue or project Entity property. The value can be either a constant, optionally including a Groovy template markup, or the result of the evaluation of a Groovy expression. To add the 'Set issue, use
Page: Set the assignee of an issue based on time in a specific time zone
When working with teams spread across multiple time zones, it may be necessary to automatically assign an issue based on the current time in a specific time zone. This becomes complicated when the time zone to be used for assignment is not necessarily the
Page: setFieldValue(String <field_name>or<field_Id>, Object value)
setFieldValue(String <field_name>or<field_Id>, Object value) method sets the value of a system or custom field of the Issue object where, <field_name> is the name of the field as displayed in the Field configuration <field_id> is the ID of the field as s
Page: Shared Action
Are you using JMWE for Cloud and want to learn how to use this post-function? Head to our documentation here https://innovalog.atlassian.net/wiki/x/XzlNC. A post-function that runs an action (a sequence of one or more post-functions), created on the Share
Page: Shared actions
Shared actions allow you to create actions that run one or more post-functions (in a sequence). These actions can then be used in the Shared Action https://innovalog.atlassian.net/wiki/x/BIC6r post-function that can be added to multiple workflow transitio
Page: Shared Groovy Scripts
This document details the Shared Groovy scripts feature of JMWE. Using this you can define global Groovy scripts that will be available from any Groovy script written in the Groovy console, post-functions, conditions and validators. This is useful for reu
Page: Shared Groovy scripts REST API
This document details the Shared Groovy Scripts REST API of JMWE using which you can import and export shared Groovy scripts within or across Jira instances. Resources Returns the JSON of the shared script by the script name. Request URL PARAMETERS parame
Page: Show custom error message on service desk request creation
This article describes how to display a custom error message on the service desk request creation screen while using the Scripted (Groovy) Validator. This is because Jira Service Desk does not display validator messages properly (https://jira.atlassian.co
Page: Sprint interface
This document details the methods of the Sprint https://docs.atlassian.com/jira-software/6.0.7/com/atlassian/greenhopper/service/sprint/package-summary.html interface you can use on a Sprint, such as those returned by the Getters https://innovalog.atlassi
Page: Standard JIRA fields
This page explains how to access the value of Standard Jira fields using Groovy. You can access them using getters of the Issue interface. To understand how to write values into the writable Standard Jira fields see Raw value/text input for fields and Gro
Page: Status interface
This document details the methods of the Status https://developer.atlassian.com/static/javadoc/jira/reference/com/atlassian/jira/issue/status/Status.html interface you can use on a status, such as those returned by the Getters https://innovalog.atlassian.

T

Page: Tempo account interface
This document details the methods of the Tempo Account interface you can use on a Tempo account, such as those returned by the Getters https://innovalog.atlassian.net/wiki/display/JMWE/Accessing+the+fields+of+an+issue when you access the Tempo Account fie
Page: Transfer JMWE configuration between instances using Botron Configuration Manager
Botron Configuration Manager for Jira https://marketplace.atlassian.com/apps/1211611/configuration-manager-for-jira?hosting=server&tab=overview is a third-party app that can be used, among other things, to transfer Jira configuration and data between diff
Page: Transition Current Issue
Are you using JMWE for Cloud and want to learn how to use this post-function? Head to our documentation here https://innovalog.atlassian.net/wiki/x/SoCcBQ. A workflow post-function that triggers a transition on the current issue. This can be used to move
Page: Transition linked issues
Documentation for is available here. A workflow post-function that triggers a transition on all issues linked to the current issue through a selected link type. This post-function does not work with remote links (links to Jira issues residing on another J
Page: Transition parent issue
Are you using JMWE for Cloud and want to learn how to use this post-function? Head to our documentation here https://innovalog.atlassian.net/wiki/x/ToCcBQ. A workflow post-function that triggers a transition on the parent issue of the current issue. To ad
Page: Transition related issues
Are you using JMWE for Cloud and want to learn how to use this post-function? Head to our documentation here https://innovalog.atlassian.net/wiki/x/TICcBQ. Documentation for is available here. A workflow post-function that triggers a transition on all iss
Page: Transitions activity tab on issue view page
The JMWE app provides an overview of the transitions triggered on the issue on the issue view page under the Activity section. This tab is visible by default. You can enable it or disable it globally, or enable it conditionally using one of the options be
Page: Troubleshooting and support for Jira Misc Workflow Extensions
This document details the troubleshooting and support options applicable to the Jira Misc Workflow Extensions add-on and is intended for Jira administrators. If you encounter problems with a JMWE workflow extension, the easiest way to investigate is to re
Page: Tutorial on looping over collections
This tutorial will guide you through writing Groovy scripts that loop over collections. The snippets in this tutorial can be further simplified using Closures, explained in the next tutorial. On this page: Looping over a collection to find values that sat
Page: Tutorial on performing an action based on the value of a field
This tutorial will guide you through writing Groovy scripts that access a field of an issue, compare it with another value, and perform an action based on the outcome. Note that you need not create a new condition/post-function/validator for the tutorial
Page: Tutorial on safe access to a field
When you access the field of an issue, you might need to verify that it is not null before calling a method on the value of the field. This tutorial will guide you through writing Groovy scripts that access the fields of an issue avoiding exceptions due t
Page: Tutorial on using Closures
This tutorial will guide you through writing Groovy scripts using Closures. On this page: Looping over a collection to find values that satisfy a condition This section of the tutorial guides you through writing a Closure to count the options of a multi-v

U

Page: Uncheck/Unselect an option
Abstract This code snippet unchecks a specific value of a standard or custom multi-valued type field (typically a multi-select field https://innovalog.atlassian.net/wiki/display/JMWEC/User+created+custom+fields). The multi-valued fields can either be a co
Page: Uninstallation
This section explains how to remove the Jira Misc Workflow Extensions add-on from your Jira instance. To uninstall, follow these steps: Log in to Jira as an administrator. Click on the Administration icon image2016-5-12 13:47:36.png. Navigate to Add-ons >
Page: Unlink issues from the current issue
Are you using JMWE for Cloud and want to learn how to use this post-function? Head to our documentation here https://innovalog.atlassian.net/wiki/x/lTlNC. A post-function that will unlink issues from the current issue based on the result of a Groovy condi
Page: Use Cases
This section lists out the use cases for the conditions, validators and post-functions of the add-on. Click on each page for the use cases: Use cases for conditions Use cases for validators Use cases for post functions
Page: Use cases for conditions
This section has use cases that help you understand the usage of the Conditions provided by JMWE. On this page: Current Status Condition This condition can be used to hide/show a particular transition from the list of available workflow actions, based on
Page: Use cases for post functions
This section has use cases which help you in understand the usage of Post-functions provided by JMWE. On this page: Assign to role member This post function can be used to assign an issue to the member of a selected project role Sample use cases: On the
Page: Use cases for validators
This section has use cases which help you in understand the usage of Validators provided by JMWE. On this page: Field has been modified validator This validator can be used to block the user from progressing to a destination status unless a field has been
Page: User Condition
A workflow condition that allows you to hide/show a particular transition from the list of available workflow actions based on either the current user or users in a specific field meeting certain criteria, such as being the reporter or assignee, belonging
Page: User created custom fields
This page explains how to access the value of User-created custom fields of different field types using Groovy. You can access them using the getters of the Issue interface. However, accessing custom fields using the native Jira API can be much more comp
Page: User Validator
A workflow validator that can validate that either the current user or users in a specific field meet certain criteria, such as being the reporter or assignee, belonging to certain groups or project roles, satisfying a Groovy condition, etc. To add a 'Use

V

Page: Validate cascading field - The parent option is mandatory and the child option, if exists, is required.
This article provides the code snippet to validate a Cascading field - The parent option is mandatory and the child option, if exists, is required using Scripted (Groovy) Validator (JMWE app) https://innovalog.atlassian.net/wiki/spaces/JMWE/pages/73302028
Page: Validators
1 - Field has been modified Validator (new in 1.3) A validator that forces users to modify a field during a transition. 2 - Field is Required Validator (new in 3.1.1) A validator that forces a field to have a value during a transition. You can optionally
Page: Variables and functions used in a Groovy expression
When running Groovy scripts, JMWE makes contextual information available to your script through built-in variables, functions, Component/Service Manager and Jira Standard Services. This document details them. Note that you can also define custom variables
Page: Version interface
This document details the methods of the Version https://developer.atlassian.com/static/javadoc/jira/reference/com/atlassian/jira/project/version/Version.html interface you can use on a version, such as those returned by the Getters https://innovalog.atla
Page: VpOrigin interface
This document details the methods of the Customer Request Type interface you can use on a request type of a Service Desk issue, such as those returned by the Getters https://innovalog.atlassian.net/wiki/display/JMWE/Accessing+the+fields+of+an+issue when y

W

Page: Workflow Conditions
Conditions control the availability of a transition to be triggered by the user. Jira Misc Workflow Extensions makes the following Conditions available to Jira administrators: Workflow Conditions
Page: Workflow Extensions
Jira Misc Workflow Extensions provides advanced workflow conditions, validators and post-functions that allow you to build sophisticated workflows without needing to dive deep into Java or Groovy coding and complex Jira APIs. Workflow Conditions Workflow
Page: Workflow Post-functions
Post-functions are used to carry out additional processing, after a transition is performed. Jira Misc Workflow Extensions makes the following Post-functions available to Jira administrators: Workflow Post-functions
Page: Workflow Validators
Validators are used to validate the input made on the transition screen after the transition is triggered. Jira Misc Workflow Extensions makes the following Validators available to Jira administrators: Workflow Validators
Page: Worklog interface
This document details the methods of the Worklog https://developer.atlassian.com/static/javadoc/jira/reference/com/atlassian/jira/issue/worklog/Worklog.html interface you can use on a work log, such as those returned by the Getters https://innovalog.atlas
Page: Writing your first Groovy script
This tutorial will guide you through writing your first Groovy script. Let us write a simple Groovy script for the functional use case: Store the author who approved an issue into a User picker custom field You can do this by adding the Set field value p

X

Y

Z

!@#$

  • No labels