6. Event-based Actions


By now, you already know that regular workflow post functions run on transitions - that is, when an issue transitions from one status to another (for example, an issue transitions from OPEN to IN PROGRESS). However, what if important issue updates occur outside of status changes - without a transition taking place? 

With Event-based Actions, you can run any of the JMWE post functions (or sequences of post functions) outside of Jira workflows. These actions can be triggered by:

  • Issue Field Value Change
  • Issue Commented
  • Issue Updated
  • Issue Created
  • Issue Transitioned

​For example, when a user updates an issue or modifies certain fields, it can trigger a rule to:


See how easy it is to configure Event-based Actions:

  

Keep in mind that even if you use Jira's built-in automation rules, you can still benefit greatly from using JMWE's Event-based Actions - see how you can shatter Jira's workflow limitations with JMWE.


Read the documentation


 

11. Additional resources

 
While we've covered most of the JMWE features, this guide is only a starting point. If you haven't done so yet, why not configure a few automations using JMWE? You can automate virtually any number of use cases, and you can make Jira work smarter for your organization.

 
Below use cases by Rachel Wright - Strategy for Jira - describe detailed implementation steps for JMWE for Jira Data Center/Server. However, the same steps would apply to Jira Cloud.


Learn more about JMWE for Jira Cloud:


Workflow Cheat Sheet

JMWE Buyer's Guide 

JMWE Product Validation

 


Thank you for exploring this Getting Started Guide! If you have any comments or suggestions on how we can improve it, please let us know

 

 

5. Sequence of Post-functions


In Jira Cloud, during a transition, all post-functions run in parallel. Often, however, you need actions to be executed in sequential order. This post-function, Sequence of Post-functions, allows you to combine several JMWE post-functions into one sequence so that they can all run in a predefined order.

For example, if you need, during a transition, to first create a new issue and then send a notification email mentioning the new issue, you need to make sure that the first post-function has finished running before starting the second one. The sequence would ensure that it runs properly.

It's very easy to set up:

Just add this post function to a transition, and then you'll be able to add and reorganize other JMWE post-function right inside it. You even have an option to stop execution if one of the post functions fails.


Keep in mind that the Sequence of Post-functions guarantees the order of events and replaces the need for using the delayed execution option in other JMWE post functions. However, suppose in addition to the Sequence of Post-functions, you also have additional post functions configured. In that case, you have an option to enable delayed execution and therefore ensure that it will run after other post-functions run.


Read the documentation


 

7. Scheduled Actions


Regular workflow post-functions run on transitions. However, with Scheduled Actions, you can schedule one or more JMWE post-functions to run against issues returned by a JQL search. For example, you can automatically transition any issue escalated yet not addressed for over 24 hours.

 

Every morning, send a reminder email to the assignee of each issue that is "in progress" status.

Viewing time 3 min 7 sec  


Things to know about Scheduled Actions:

  • ​Works based on predefined times, not based on workflow transitions.
  • Flexible scheduling allows for any frequency (10-minute minimum).
  • Can execute many types of automations, such as workflow transitions, issue status and user changes, all in sequence.

For your convenience, the steps from the above video have been outlined below.

  

Every morning, send a reminder email for each "in progress" issue.

  • Go to the "Scheduled actions" page of the JMWE app.
  • Press "New scheduled action".
  • Add a name "Remind assignees."
  • Select the schedule, 9 am every day in our case.



  • In Target Issues, JQL expression, press "Edit JQL" to specify which issues will be affected by this rule.
  • Specify JQL search; in our case, specify: status = "In Progress". Press "Search." The results will be displayed so you can verify your input.
  • Press "Submit."



  • Optionally: select the maximum number of issues to process to maintain good Jira performance.
  • Then "add post function" to specify which action to undertake per our selected schedule.



  • Add a post function called "Email issue". Specify email content.



  • Select Issue members as "Assignee," and Save.



  • Save Scheduled Action.



You now have an action scheduled to run every morning, at 9 am, to remind users of their In Progress issues.

See it all in action in the video above.


Read the documentation


8. Transition History Tab


Jira Misc Workflow Extensions (JMWE) includes the Transitions history tab in the Activity section on the Issue View screen. It lets users easily see all issue status transitions, when and by whom they were triggered, all in one list. They can also see Time in status for each transition to easily evaluate status changes of an issue.
 

 

Users can view the following for each transition:​

  • Transition statuses. It lists To and From statuses of transitions in chronological order. (Note, since auto-transitions don't change the issue status, JMWE does not show them).
  • When the transition was triggered (with timestamp). You can hover over the date to see the full timestamp value, which is especially useful for relative date/time values.
  • Author of the transition.
  • Time in Status. How long the issue spent in the original "from" status (left of the arrow) before being transitioned.

 

Users can find this information by navigating to the issue details screen in the section called "Transitions".


How to disable it:

The JMWE Transitions tab is enabled by default, but you can also turn it off to remove it from user views. If you choose to hide the JMWE's Transition tab, uncheck the option on the configuration page of the JMWE app.


Read the documentation