Cloud Migration Resources
Planning a Jira Cloud migration? These resources can help you get started:
→ JMWE Cloud features – Review Cloud features and understand key differences between DC and Cloud.
→ Migration support from Appfire – Learn how we can help you migrate smoothly.
Scheduled actions
A Scheduled action is a series of one or more JMWE post functions that run according to a schedule; the Scheduled Action runs against issues returned by a JQL query. These actions are useful in performing automated execution of post functions at specific times on selected issues of your Jira instance. For example:
Send emails automatically every day
Create a new subtask every week
Update issue with information from another Jira instance every hour
To access Schedule actions:
Log in to your Jira instance as an administrator.
Click the Settings icon in the upper right corner and select Apps.
Under JIRA MISC WORKFLOW EXTENSIONS in the left-hand panel, click Scheduled actions.
The Scheduled Actions page (Figure 1, right) lists all Scheduled Actions that have been created, as well as the following:
Search - Filter the list of Scheduled actions by action name.
Create new action - Click to create a new Scheduled Action.
Shared action list - A list of all Scheduled Actions for the instance. The list includes the following information:
Enabled - Status of a Scheduled Action. By default, a newly created Scheduled Action is enabled.
Action name - The name of the Scheduled Action. Click the name to edit the Scheduled Action.
Schedule (in UTC time) - Interval at which a scheduled action is performed. When you hover over the schedule, its next run is displayed in UTC time.
By - The user who created the action, or the last user to edit or enable/disable the action.
Last modified - When the action was last modified (edited or enabled/disabled).
Post-functions - Displays the number of post functions included in the Scheduled Action.
Hover over the badge to see a list of the post functions included in the Shared Action.Executions - An icon representing the status of the last execution. If the action encountered an error or warning, hover over the icon to see more information.
Action menu - Click to open a menu with specific actions for the Scheduled Action:
Duplicate - Create a copy of the Scheduled Action. The new Scheduled Action will have the same name as the original, with “- copy” appended.
Run now - Run the Scheduled Action manually.
View Summary - Open the Summary window (Figure 2, right), listing the schedule for the action, the JQL query used for the Target issues, and the Post-functions included in the Scheduled Action.
ID - The Jira ID of the Scheduled Action. Click the menu option to copy the ID value to your clipboard. This value can be used in the JMWE Logs page to filter the logs by Action ID.
Delete - Permanently delete the Scheduled Action.
Show obsolete only
As noted in Deprecated post functions, changes to Atlassian’s infrastructure require that deprecated JMWE post functions be completely removed by the end of September 2025. Please review the documentation on how this impacts your automations and how to update your workflows and Actions to the current versions of each deprecated post function.
Check this box to filter the display of Scheduled actions to only display actions that include deprecated post functions. The checkbox includes a number indicating how many deprecated post functions exist across all Scheduled actions.
Filter and Sort
Configure a Scheduled Action
When you create or edit a Scheduled Action, the Scheduled Action Editor will open (Figure 3, right). The Scheduled Action Editor uses the JMWE Automation Rule Builder, consisting of two side-by-side panels; the left panel has buttons for selecting each configuration category (e.g. When for the Scheduled Action schedule), and the right panel includes specific configuration options for the selected category.
To configure a Scheduled Action set the following configurations:
Action name (Point 1, Figure 3, right) - Required. Click the name to edit. Enter a meaningful name and hit Enter, or click the check button, to save.
Description (Point 1, Figure 3, right) - Click Add a description to edit the Scheduled Action description. Enter a detailed explanation of the action and click the check button to save.
When/Schedule (Point 2, Figure 3, right) - Click the When header or the Schedule button. In the right panel, click each field to set the schedule for the action. See Schedule, below for more information.
If Scope/Target Issues (Point 3, Figure 3, right) - Click the If Scope header or the Target Issues button to configure the JQL query that will return the issues for the Scheduled Action; set Max Issues to limit the number of issues for the action. You can test your query and preview the results by clicking the Search button. See Target Issues, below, for more information.
Who (Point 4, Figure 3, right) -
Then/Post-functions (Point 5, Figure 3, right) - Click the Then header or the Post-functions button. In the right panel, select a post function from the list to add the first post function, or click Add post-function to add additional post functions. See Post-functions, below for more information.
Skip subsequent post-functions if a post-function encounters an error - Check this box to stop the execution of the Event-based Action if any of it’s post functions encounter an error.
Click Save to save the Shared Action.
Schedule
The Schedule configuration determines how often the action will run. Every time the action runs, that action’s JQL search will run, and the post functions included in the action will run on each issue returned by the search, both in order of the issues returned by the JQL query and the order of the post functions within the Scheduled Action.
Please note the following limitations on Scheduled Actions:
You cannot run a scheduled action more than once every 10 minutes and running scheduled actions too often will have an impact on the performance and responsiveness of your Jira instance.
In general, there will be a difference of a few minutes in the configured scheduled time and the actual execution time of the action. For example. if you configure a Comment issue post function in the scheduled action to run every hour, then the comment might be added at 10:02 AM and then at 11:01 AM and then at 12:02 AM, etc.
The greater the number of actions that are scheduled, the more the actual execution time will vary. Actual execution time and execution duration depend on how many scheduled actions are running at the same time.
Configure a schedule
You can run the Scheduled Action at nearly any interval ranging from every hour to every year at specific times.
Note that the schedule is expressed in UTC time.
The available values for the Schedule will change based on the increment that is initially selected. To set the schedule for an action set each of the available fields:
Increment - Set the overall increment. Available options are hour, day, week, month, or year.
The other values for schedule will change based on this selection.Hour and/or Minute - All increments allow for the Scheduled Action to run at a specific time of day.
Hours are set using a 24 hour clock.
Multiple hours or minute values can be selected. For example, to run an action every day at 6 AM and 3 PM every day, set the field as pictured below.
Day of the Week - Available when the increment is set to week. Set the day or days of the week (Monday through Sunday) when the action will run.
Day of the Month - Available when the increment is set to month or year. Set the date or dates of the month when the action will run.
Please note, the default value for this field is ‘Every day of the month’. To set this field back to the default value, deselect all of the specific dates.Month of the Year - Available when the increment is set to year. Set the month or months when the action will run.
Please note, the default value for this field is ‘every month’. To set this field back to the default value, deselect all of the specific months