robotsnoindex

Actions are the doers of your rule. They allow you to automate tasks and make changes within your site, and can perform many tasks, such as editing an issue, sending a notification, or creating sub-tasks.

See how to use all of these actions in our Jira automation template library.

Assign Issue

  • Use smart values here: Yes

  • Required permissions: Assign issues, Assignable user

Assigns an issue to a user.

There are eight different options for assigning issues:

  • A user in a defined list: An issue that passes a restriction (specified in JQL) is assigned to a user from a specified list of users using the method of your choosing. This can be:

    • Balanced Workload: Ensures that each user in the list has the same number of issues assigned.

    • Random: Assigns randomly from the list of users.

    • Round-Robin: Assigns issues based on the sequence in the list of specified users.



  • Another field value or comment: Assign the issue based on user field values on the issue or in a comment. For example, assign the issue to a previous assignee based on the issue history, or assign the issue to its creator. If you specify users to exclude, or groups the user must be in, any user not matching this requirement will be skipped and the action will continue looking for matching users (such as going further back in the issue history of assignees).

  • Automatic: Assign the issue to the project's default assignee.

  • Copy from another issue: Copy the assignee from a related issue. You can also use JQL to find an issue to copy the assignee from.

  • Smart value: Assign the issue based on a smart value. For example, when an issue is commented on, you can assign it to the author of the comment.

  • Specify user: Assign to a selected user.

  • Unassigned: Set the issue to be unassigned.

  • User who triggered the event: Assign the issue to the user who triggered the event.

Clone issue

  • Use smart values here: Yes

Creates a duplicate of an issue within the same project or a project of your choosing.

This action can be used as part of a workaround for moving issues between projects.


This action will create a new issue and copy across all field data possible. Its status is then set to the first step of the corresponding workflow, and any resolutions from the original issue will be cleared. As the issue is not a true clone, it won’t be linked to the original issue.

You can also set values to override any copied data in supported fields. Select More options to display additional fields for advanced field editing.

This action will not clone issue links, comments or attachments.


Comment on issue

  • Use smart values here: Yes

Adds a comment to an issue.

You can use smart values to reference issue fields to personalize the comment. You can also set the comment visibility.


Create issue

  • Use smart values here: Yes

  • Required permissions: Browse projects, Create issues

Creates an issue of any type to a project.

You can select fields to configure, and set their values. Select More options to display additional fields for advanced field editing.

Take care when using Project > Same project as trigger on global rules. As the project type is unknown until the rule runs, all issue types are available to configure. This means that you can select an issue type that will not exist in the project.


Create sub-tasks

  • Use smart values here: Yes

Creates sub-tasks on an issue.

This action only supports setting the Summary of the sub-task.

Selecting Add fields will convert the Create sub-tasks action into a Create issue (issue type: sub-task) action, allowing you to set additional fields.


Create variable

  • Use smart values here: Yes

Define your own smart value, which can be used in other actions and conditions in the same rule. The smart value you define can consist of other smart values, as well as math functions.


Delete comment

  • Use smart values here: Yes

Can only be used with a trigger that involves adding a comment, such as Issue commentedIssue transitioned, or Issue updatedThis action deletes the comment that triggers its rule.

The only input that can be used is {{comment.id}}.

Delete issue

  • Use smart values here: No

Deletes the current issue that is in context.

This action allows you to remove unwanted issues from your site, such as when automating moving issues between projects.

Deletes the current issue that is in context. This is a great way to remove unwanted issues from Jira, such as in automating moving issues between projects.


  • Use smart values here: No

This action allows you to remove any issue links currently on an issue. You can remove all issue links of a certain type (for example, remove all "blocked by" issues), or select specific issues to unlink.

Edit issue

  • Use smart values here: Yes

Edit the current issue by choosing the field to set and value to add.

You can set some values to be dynamic. Select More options to display additional fields for advanced field editing.


Link issues

  • Use smart values here: Yes

Links an issue to another by selecting the link type and the issue to link.

You can link to the issue that trigger the rule, the current issue on a related issues branch, a smart value or an issue key.


Log work

  • Use smart values here: Yes

Logs time against an issue.

You can use date and time smart values to dynamically set the date started, and text smart values to customize the description.


Lookup issues

  • Use smart values here: Yes

Search for up to 100 issues using a JQL query. Include the results list in other actions by using the {{lookupIssues}} smart value. Learn more about using smart values with issue lists.

From the resulting issue list, the following issue properties are available to use (custom fields aren't available):

  • {{key}} - Returns the issue key

  • {{url}} - Returns the issue url

  • {{summary}} - Returns the issue summary

  • {{assignee.displayName}} -  Returns the assignee

  • {{reporter.displayName}} -  Returns the reporter

  • {{status}} - Returns the status

  • {{issueType}} - Returns the issue type

  • {{resolution}} - Returns the resolution status

  • {{fixVersion}} - Returns the fix version

  • {{created}} - Returns the date the issue was created

  • {{updated}} - Returns the date the issue was updated

  • {{Story Points}} - Returns the story points for the issue (classic Jira Software)

  • {{Story point estimate}} - Returns the story points for the issue (next-gen Jira Software). Learn more about using smart values with numbers.

For example, to print the issue key for each issue in bullet point form:

{{#lookupIssues}}
* {{key}}
{{/}}


And the following example sums all story points in the issue list:

There are {{lookupIssues.Story Points.sum}} story points remanining.

Manage watchers

  • Use smart values here: Yes

Add or remove watchers on an issue.

You can specify users to add or remove by using smart values directly in the fields.


Transition issue

  • Use smart values here: Yes

Transitions an issue from one status to another, through a workflow.

You can select field to update as part of this transition, for example:

  • Copy from issue: copies the status from a related issues or an issue on a branch rule.

  • Copy from parent: for use with sub-tasks; copies the status from a parent.

  • Copy from Epic: copies the status from the issue's associated Epic.

  • Copy from Trigger issue: copies the status from the issue that triggered the rule.

  • Same status (loop): for use when a transition exists from the current status back to itself; this can be used together with a screen to gather more data from users, e.g. an Escalate transition.


Send email

  • Use smart values here: Yes

Sends an email.

All the fields on this action support customization using smart values.


Send Microsoft Teams message

  • Use smart values here: Yes

Sends a Microsoft Teams message to notify a team when a rule is run

You can personalise the message in this action. Learn more about using automation with Microsoft Teams.


Send Slack message

  • Use smart values here: Yes

Sends a Slack message to notify a team or individual when a rule is run

You can personalise the message in this action. Learn more about using automation with Slack.


Send Twilio (SMS) message

  • Use smart values here: Yes

Sends a notification using the Twilio service.

This action is useful for service teams that rely on SMS for on-call scenarios.


Send outgoing web request

  • Use smart values here: Yes

Sends an outgoing web request to notify another system when a rule is run.

You can set this action to return response data that can then be used in a subsequent action.


Add Jira Service Management customer

  • Use smart values here: Yes

Adds new customers to your Jira Service Management project.

You can use smart values in all fields and add the customer to an existing organization.



Calling this action multiple times in quick succession will result in the first call succeeding and then subsequent calls failing due to the customer existing but not yet showing up in user search results. It can take up to 15 seconds for the new user to appear in searches and this to resolve itself.

The {{customer}} smart value will not return the existing user until they are available in the user search results and the action will result in an error.

If this issue is affecting your rule, you can introduce a delay into your rule by adding a number of Re-fetch issue data actions right before the Add Service Project customer action – note that this may not work in all cases.

Create Jira Service Management request

  • Use smart values here: Yes

Creates a new Jira Service Management request.

Similar to the Create issue action, this action allows you to configure any field available using smart values.


Create version

  • Use smart values here: Yes

Creates a new version that you can assign issues.

If a version with the same name already exists, the version will not be created.


Release version

  • Use smart values here: Yes

Releases a version.

By default, this action will release the next unreleased version of a project with the existing release date. This is determined by the order the versions are set in Releases.

You can select a specific version to release, and use smart values to set dynamic names.


Delete attachments

  • Use smart values here: Yes

Cleans up attachments using regular expression matches, based on the attachment filename.


Log action

  • Use smart values here: Yes

Logs a value to the audit log.

This action is useful when testing smart values, and debugging rules.


Re-fetch issue data

  • Use smart values here: No

Refreshes smart values with the latest field values.

By default, the {{issue}} reference is not updated during rule execution, and contains the same values as when the rule originally triggered.


Set entity property

  • Use smart values here: Yes

Sets entity properties on issues, projects and users related to the trigger issue of the rule execution.

These hidden properties can be used by apps for certain functions. Entity properties allow plugins to add key/value stores to issues and projects. These values can be indexed and queried via REST API or JQL.


Unrelease version

  • Use smart values here: Yes

Unrelease a released version for a chosen project. By default, this will be the rule's project, but you can select More options to choose a different project.