Jira Misc Workflow ExtensionsFor Jira Cloud

Implementing advanced workflows without code

Start Free Trial Now

 

Building Workflows Without Code

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. JMWE for Jira Cloud provides a collection of advanced post-functions giving you all the building blocks you need to extend your workflows without code to support any number of business use cases.

Below you can view the list of JMWE post-functions (as well as Jira pre-installed optional post-functions). For the most updated list and for more information, please refer to this page in the documentation

Workflows for JIRA Server
 

image

Atlassian Verified

 

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 Entity 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 provided either as text (with optional Nunjucks annotations) or as a JSON value.

Set field value of linked issues 

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 provided either as text (with optional Nunjucks annotations) or as a JSON value. 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.

Copy field value to parent issue 

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 issue 

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, from an Epic to its Stories, etc.

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

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 Nunjucks 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 simple text or the result of the evaluation of an arbitrary Nunjucks script.

Comment linked issues 

Creates a Comment on linked issues. The text of the comment can be either a simple text or the result of the evaluation of an arbitrary Nunjucks 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 member of a selected 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 last 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 current issue 

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