image

JIRA Misc Workflow Extensions  |  For JIRA Cloud
 

No-code solution for implementing advanced workflows

From only $5 /month

Start Free Trial Now

 

"Consistently useful functionality. One of the best plugins out there."

Matt Doar (CustomWare)

Rapidly Implement Complex Workflows, Without Code

JMWE removes the limitations of JIRA’s built-in features to allow you to quickly build sophisticated workflows to support business-critical processes of your users.

Workflows help teams improve efficiency and when properly customized to fit the business needs, they become essential for the success of the overall organization. A workflow can be as simple as moving an issue from todo to in progress to done, and as complex and elaborate as your business process requires - in either case, workflows are designed to deliver efficiency to tasks that users perform on a regular basis.

JIRA offers good starter features, but when you want to build sophisticated workflows to truly fit the needs of your team, you will want to customize further. This is where JIRA Misc Workflow Extensions (JMWE) comes in - it helps you automate business processes through more advanced workflow functionalities. JMWE for JIRA Cloud provides a collection of advanced post-functions giving you all the building blocks you need to extend your workflows quickly and without code.

View Pricing

JMWE powers workflows for millions of users

Whether you are a software developer tasked with JIRA management or a dedicated JIRA administrator, JMWE provides you with an effective and simple solution to quickly implement sophisticated workflows.

Get Started Now

image

JIRA includes several workflow post-functions. JMWE for JIRA Cloud offers a wide selection of 'premium' post-functions that can be added to transitions.

Building Workflows with JIRA and JMWE for JIRA Cloud

Workflows are essential for the success of the business. They automate business rules to auto-assist users in deciding when one step has been completed successfully and the next step can begin.

Every JIRA Cloud transition has the following essential post-functions:

  • Set issue status to the linked status of the destination workflow status.
  • Add a comment to an issue if one is entered during a transition.
  • Fire an event that can be processed by the listeners.
  • Update change history for an issue and store the issue in the database.
  • Reindex an issue to keep indices in sync with the database.

These essential post-functions cannot be deleted from a transition. However, you can insert a few other post functions that are available with native JIRA installation.

Below you can view the list of JIRA pre-installed standard post-functions, as well as those that are made available by purchasing JMWE for JIRA Cloud. 

Field Updating Post-Functions

JIRA standard post-functions

  • Update Issue Field (*DOES NOT UPDATE CUSTOM FIELDS) - Updates one of the issue's fields to a given value. Fields that can be updated include: Assignee, Description, Environment, Priority, Resolution, Summary, Original Estimate, Remaining Estimate.

JMWE post-functions

Increase value of field

Increases the value of a numerical field by one

Set field value from user property value

Sets the value of a selected field of the current issue to the value of a User Property of the current user.

Set field value

Sets the value(s) of a selected field of the current issue. The value can be either a constant or the result of the evaluation of a Groovy expression or the result of a Groovy template.

Copy field value to parent 

Copies the value(s) of a field into the same field of the issue's parent issue.

Add field value to parent 

Adds the value(s) of a multi-valued field (such as Fix version(s)) into the same field of the issue's parent issue or from an Epic to its Stories (or vice-versa).

Copy field value from parent 

Sets a field value to the value(s) of the same field of the issue's parent issue.

Copy field value to linked issues 

Copies the value(s) of a field into the same field of all issues linked to it through a specified link type. You can also use this function to copy a field from an issue to its sub-tasks by using the built-in "jira_sub_outward is Parent of" link type.

Copy value from field to field

Copies the value(s) of a selected field to another field of the same issue.

Create/clone issue

Creates a new issue. The specifications of the issue to be created can be customized using the options provided.

Copy field value from linked issues 

Sets a field value to the value(s) of the same field of an issue linked to it through a specified link type.

Set field value of linked issues 

Sets the value(s) of a field on all issues linked to the current issue through a specified link type. The new value can be either a constant or the result of the evaluation of an arbitrary Groovy script. You can use this function to set the value of a field on the Epic of an issue, or on all issues of an Epic. You can also use this function to set a field of all sub-tasks.

Set issue security from user role 

Sets the issue security level based on the Project Role to which the current user belongs.

This function can be used on the Create transition to set a different issue security level depending on whether the issue is being created by an internal user or by an external user (e.g. a customer)

Scripted (Groovy) operation on issue

Executes an arbitrary Groovy script against the current issue.

Link issues to the current issue

Links the current issue to all issues that satisfy a parameterized JQL query.

Unlink issues from the current issue

Unlinks issues from the current issue based on the result of a Groovy condition.

 

Communications Post-Functions

JIRA standard post-functions

  • None

JMWE post-functions

Email issue 

Sends an email to certain recipients specified in the post-function configuration.

Comment issue 

Creates a Comment on the current issue. The text of the comment can be either a fixed text, or the result of the evaluation of an arbitrary Groovy script.

Comment linked issues 

Creates a Comment on linked issues. The text of the comment can be either a fixed text, or the result of the evaluation of an arbitrary Groovy script.

 

Assignment Post-Functions

JIRA standard post-functions


  • Assign to current user - Assigns the issue to the user who is executing the transition.
  • Assign to lead developer - Assigns the issue to the component lead, if one exists, or project lead.
  • Assign to reporter - Assigns the issue to the user who created the issue.

JMWE post-functions


Assign to role member 

Assigns the current issue to the default member of the specified project role.

This can be used for scenarios like: "when a developer resolves the issue, assign the issue to the QA lead".

Assign to last role member

Assigns the current issue to the latest Assignee (excluding the current one) who is a member of the specified project role. If it finds a user that belongs to the specified role, it assigns the issue to that user. Optionally, it can consider the Reporter and/or the Current Assignee in addition to previous assignees.

This can be used for scenarios like: "when QA fails to assign the issue to the last developer who worked on it".

 

Transition Triggering Post-Functions

JIRA standard post-functions

  • None

JMWE post-functions

Transition Issue 

Triggers a named transition on the current issue. This can be used to move the current issue one step further in the workflow, if a condition is fulfilled.

Transition parent issue 

Triggers a named transition on the parent issue of the current sub-task.

Transition linked issues 

Triggers a named transition on issues linked to the current issue through a specified link type. The Transition Linked Issues post-function can also be used to transition sub-tasks.

More information on post-functions can be found here.