---
title: "Scheduled actions"
canonical: "https://support.appfire.com/space/JMWEC/466321868/Scheduled%20actions"
format: markdown
---
> Macro (aura-html)

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.  
:note: **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](https://appfire.atlassian.net/wiki/spaces/JMWEC/pages/466321741) page to filter the logs by **Action ID**.
    - **Delete** - Permanently delete the Scheduled Action.

![JMWE for Jira Cloud scheduled action summary interface with action overview](media://0163c04a-6282-4c65-a2eb-b4b7080c140d)

## Show obsolete only

> ⚠️ As noted in [Deprecated post functions](https://appfire.atlassian.net/wiki/spaces/JMWEC/pages/542803231), 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

> Macro (include)


## Post-functions

![JMWE for Jira Cloud scheduled action post functions configuration panel](media://f5299732-8cdc-4205-a1d3-a616e120daea)

For each issue returned by the JQL search (detailed above), the configured post functions will run *in the order in which they are listed*. 

### Add a post function

1. In the right panel, click **Add post function** at the top of the panel.
2. Select a post function from the list and click **Add**. You can search for the post function by name using the Search field at the top of the list.
3. The post function configuration window will open. Configure the selected post function as needed, then click **Save**. See [Post functions](https://appfire.atlassian.net/wiki/spaces/JMWEC/pages/465242045) for more details on all of the available post functions.

### Modify or delete a post function

The steps to modify or delete a post function depend on the post function view you are using. See **Post function views** directly below for more information.

## Passing variables within a sequence

It is possible to pass data from one post function to all subsequent post functions within a Scheduled Action by using the `{% setContextVar %}` Nunjucks tag. When using a Build-your-own (scripted) post function, the variable can be set anywhere within your script; when using other post functions, the most common place to set a variable is in the **Conditional Execution** configuration. 

- **context:** Holds all the *context variables* added in the current post function. For example, if you create a context variable `myVar` in the first post function of the sequence:
  This variable will then be available to all its subsequent post functions as:

> ⚠️ **Please note**: a variable created in a post function will not be available in the Nunjucks tester if you are attempting to test additional post functions that are to be added after the one where the variable was originally created.

**Variables specific to the Create Issue post function**

- `newIssueKey:`** **Stores the issue key of the *last* issue created by a [Create Issue(s)](https://appfire.atlassian.net/wiki/spaces/JMWEC/pages/466256916) post function in the action. You can access it as:
  
- `newIssueKeys:`** **Stores an array of the keys of all the issues created by any [Create Issue(s)](https://appfire.atlassian.net/wiki/spaces/JMWEC/pages/466256916) post function in the action. You can access the created issues from:
  For example: to add a comment on the current issue with the keys of the issue created previously:
  

You can access the information of a specific issue using the [issue](https://appfire.atlassian.net/wiki/spaces/JMWEC/pages/465373638) filter. For example: To get the assignee of the issue created by the [Create Issue(s)](https://appfire.atlassian.net/wiki/spaces/JMWEC/pages/466256916) post function:

```javascript
{{ context.newIssueKey | issue("assignee") | field("fields.assignee.displayName") }}
```