JIRA Misc Workflow Extensions  |  For JIRA Server

No-code solution for implementing advanced workflows

From only $10 for 10 users

Start Free Trial Now


"A MUSTHAVE plugin for all JIRA administrators!"

Dominic Finke

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 Server provides a collection of workflow conditions, post-functions and validators giving you all the building blocks you need to extend your workflows quickly and without code.

Explore All Features

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


Using JMWE’s conditions, validators and post-functions, you can build...

  • Sequential workflows that progress from one stage to next and do not step back;
  • State workflows that progress from ‘State’ to ‘State’ - these workflows are more complex and return to a previous point if required;
  • Rules-driven workflows, which are implemented based on a sequential workflow, where the rules dictate the progress of the workflow

View Pricing


Validators check that any input made to the transition is valid before the transition is performed.

Enforce custom rules on data that must be inputed during a transition, such as requiring that a field is modified, a comment is provided, or a multi-select field has a single value.

  • Field has been modified
  • Comment required
  • Field is required
  • Field has single value
  • Previous status
  • Parent status


Conditions control whether a transition should be executed but the user.

Disable (hide) a transition based on the previous status or the actors of an issue, or simply unconditionally hide a transition that is only used indirectly (e.g. through a post-function). 

  • Previous Status
  • Separation of Duties
  • Hide Transition


Post functions carry out any additional processing required after a transition is executed.

Assign an issue to a role member, set a field to a constant value or Groovy expression, copy field values to/from the parent issue or linked issues, and much more.

  • Assign to role member
  • Assign to last role member
  • Increase value of field
  • Set field to user property value
  • Copy field value to parent
  • Add field value to parent
  • Set field value from parent
  • Copy Field Value to Linked Issues
  • Set Field Value From Linked Issue Function
  • Set Field Value Of Linked Issues
  • Set Issue security from user role
  • Transition Issue
  • Transition Parent Issue
  • Transition Linked Issues
  • Comment Issue
  • Comment Linked Issues
  • Copy Value from Field to Field (will be available in Jira - as Copy Value From Other Field)
  • Set Field Value to constant or Groovy expression (will be available in Jira - as Update Issue Custom Field)

Explore All Features