Actions

Assign issue

This action is an easy to use and customisable way of assigning issues for most scenarios. Check out this blog post for a more in-depth explanation of this action.

There are eight different options for assigning issues:

A user in a defined list

Using this option, 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 users, assigning a user an issue and then moving on to the next user in the list

Assign Issue to a user in a list

Another field value or comment

Using this option, you can assign the issue based on some of the user fields on the issue or comments, e.g. assign it to previous assignee based on the issue history, or assign the issue to its creator. If you specify users to exclude or specify groups that the user must be in, then any user that does not match this requirement will be skipped and the action will keep trying to find a user (such as going further back in the issue history of assignees).

Automatic

The issue is assigned to the project's default assignee.

Copy from another issue

This option allows you to copy the assignee from a related issue or to write JQL to find an issue to copy the assignee from.

Smart value

Use this option to assign the issue based on a smart value using any of the user smart values. For example, when an issue is commented on, you could assign it to the author of the comment.

Specify user

Use this option to assign to a specific user of your choosing.

Unassigned

Use this option to set the issue to be unassigned.

User who triggered the event

Use this option to assign the issue to the user who triggered the event

Clone issue

  • Use smart values here: Yes
  • Available in Server Lite: No

Cloning an issue lets you quickly create a duplicate of an issue within the same project or a project of your choosing. This can also be used as part of a workaround for moving issues between projects.

Due to a lack of an available API for cloning issues, this action creates a new issue and copies across all of the fields that it can. Its status is then set to the first step of the corresponding workflow, and any resolutions from the original issue are cleared. However, as it is not a true clone, the cloned issue isn't linked to the original issue.

You can also set any supported fields to a value of your choosing that will override any copied values (see Edit additional fields for help on using additional fields in the advanced section).

Clone issue action

Limitations

Due to API limitations in Jira, this action does not clone issue links and comments (see AUT-465), or attachments in cloud (see AUT-1030). Attachments can be cloned in Server.

Comment on issue

  • Use smart values here: Yes
  • Available in Server Lite: Yes

Use this to add a comment to an issue. You can use smart values to reference issue fields to personalize the message along with setting the visibility of the comment.

Comment issue action

Create issue

Use this action to create an issue of any type in any project. You can select any number of fields and set their values (see Edit additional fields for help on using the additional fields in the More Options section). If you are working with sub tasks then you may find our blog post, creating sub-tasks with required fields, helpful.

Create issue action

TIP

  • Care needs to be taken with global rules that use the same project as trigger issue options as we do not know what the project type is until the rule runs. All issue types are available which means that you could choose an issue type that does not exist in a project.
  • Service Desk specific fields such as 'Request type', 'Request participants' or 'Organization' are only available in Jira 7.3+ and Service Desk 3.3+.

Create sub-tasks

  • Use smart values here: Yes
  • Available in Server Lite: No

A quick way to add a number of sub tasks to an issue. This action only supports specifying the summary.

Setting fields

Choosing Add fields will remove the individual sub task from the action and add a new Create Issue action where you can specify fields.

Create sub-tasks action

Delete issue

  • Use smart values here: No
  • Available in Server Lite: Yes

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.

Delete issue

Edit issue

  • Use smart values here: Yes
  • Available in Server Lite: No

Using this action you can easily edit most fields of the current issue, simply choose the field to set and add the value for it. Some of the values can be dynamic. You can also use the flexibility of additional fields in More options for those more complicated situations.

Want to create an organization for a Jira Service Desk customer? You can set this from the reporter's email domain name. Find out how in this blog post.

Edit issue action

TIP

Service Desk specific fields such as 'Request type', 'Request participants' or 'Organization' are only available in Jira 7.3+ and Service Desk 3.3+.

  • Use smart values here: Yes
  • Available in Server Lite: No

Using this action you can easily link issues, simply select the link type and the issue to link. You can use the options in the issue drop down, enter an issue key into the drop down for a specific issue or enter a smart value into the drop down for those advanced use cases. To read more on advanced use cases, check out our blog post Automatically linking issues.

Link issues action

Log work

  • Use smart values here: Yes
  • Available in Server Lite: No

With this action you can log time against an issue. You can use date and time smart values to help you dynamically set the date started and text smart values to customise the description.

Log message action

Manage watchers

  • Use smart values here: Yes
  • Available in Server Lite: No

Sometimes you just want to make sure that certain people get notified when an issue is updated. With this action you can add or remove watchers as necessary. You can also specify users to add or remove by typing {{smart values}} directly into the fields.

Manage watchers action

Transition issue

  • Use smart values here: Yes
  • Available in Server Lite: Yes

This action transitions an issue through a workflow. You can also select fields to update as part of the transition, for example:

  • Copy from issue - use this when you need to copy the status from a related issue or an issue on a branch rule
  • Copy from parent - for use with sub-tasks, sources the status from their parent
  • Copy from Epic - sources the status from the issue's associated epic.
  • Copy from Trigger issue - sources the status from the issue that triggered this rule, most useful on branches
  • Same status (loop) - for use when a transition exists from the current status back to itself, typically used in conjunction with a screen to gather more data from users (e.g. an "Escalate" transition)

Transition action

Send email

  • Use smart values here: Yes
  • Available in Server Lite: No

This action allows you to send an email. All of the fields support customisation via smart values.

In server, the default ‘from’ address in emails is Jira’s default email whereas in cloud it is always 'noreply@automationforjira.com'.

Send email action

TIP

Service Desk specific recipients such as 'Pending approvers' are only available in Jira 7.3+ and Service Desk 3.3+.

Send Microsoft Teams message

  • Use smart values here: Yes
  • Available in Server Lite: No

Notify a team when the rule is run. You can personalise the message using the provided fields. Refer to how to integrate Microsoft Teams for detailed instructions.

Microsoft action

Send Slack message

  • Use smart values here: Yes
  • Available in Server Lite: No

Notify a team or an individual when the rule is run. You can personalise the message using the provided fields. Refer to how to integrate Slack for detailed instructions.

Slack action

Send Twilio (SMS) message

  • Use smart values here: Yes
  • Available in Server Lite: No

A lot of service teams rely on SMS for on-call scenarios. With this action you can send a notification using the Twilio service.

Twilio action

Send outgoing web request

  • Use smart values here: Yes
  • Available in Server Lite: No

Quite often you need to integrate with other systems. This action allows you send an outgoing web request to notify another system when the rule is run, and optionally return response data that can then be used in a subsequent action. It is an extemely powerful action. Learn more about it in this blog.

outgoing web request

Add Service Desk customer

  • Use smart values here: Yes
  • Available in Server Lite: No
  • Minimum Jira version: Jira 7.5+ and Service Desk 3.3+

Add new customers to your Jira Service Desk project with this handy little action. You can use smart values in all fields and add the customer to one of your existing organizations.
Check out this great blog post Create customers and add JIRA Service Desk requests!

Add ServiceDesk customer action

Create Service Desk request

  • Use smart values here: Yes
  • Available in Server Lite: No
  • Minimum Jira version: Service Desk 3.3+

Creates a new Jira Service Desk request. Just like the above Create issue action, this allows you to configure any field available using smart values.

Create ServiceDesk request action

Create version

  • Use smart values here: Yes
  • Available in Server Lite: No

This creates a new version you can assign issues to. If a version with the same name already exists, no new version is created.

Create version action

Release version

  • Use smart values here: Yes
  • Available in Server Lite: No

Use this to release a version. By default, this releases the next unreleased version of a project with the existing release date. The "next version" is determined by the order you set in the "Releases" tab on your software project. You can pick a specific version to release and use a smart value to set dynamic names.

Release version action

Delete attachments

  • Use smart values here: Yes
  • Available in Server Lite: Yes

Use this action to clean up old attachments using regular expression matches based on the attachment filename.

Delete attachments action

Log action

  • Use smart values here: Yes
  • Available in Server Lite: Yes

This action logs something to the audit log. This is a great way to try out smart values and see what they return, and a great way to debug your rules.

Log message action

Re-fetch issue data

  • Use smart values here: No
  • Available in Server Lite: Yes

This action refreshes smart values with the latest field values. By default the {{issue}} reference is not updated during rule execution, and therefore contains the same values as when the rule originally triggered.

Refresh issue action
(delaying the rule execution is only available in server)

Set entity property

  • Use smart values here: Yes
  • Available in Server Lite: No

Use this to set hidden 'entity' properties on issues, projects or users related to the trigger issue of the rule execution. These properties can then be used by apps for some functions. Entity properties allow plugins to add key/value stores to Jira entities, such as issues or projects. These values can be indexed by Jira and queried via REST API or JQL.

Set entity property action

Publish event (server only)

  • Use smart values here: Yes
  • Available in Server Lite: Yes

Use this to publish Jira events (system or custom) that other add-ons and integrations can listen for.

Publish event action

Third party actions

Automation for Jira in server allows extensions contributed by other app vendors in the Atlassian Marketplace that contribute automation actions directly in our UI. For details on how to contribute these actions see our developer guide.

If you require support for the following actions, please contact the action's vendor.

The following table contains 3rd party actions you can automate with Automation for Jira. Check our developer guide for details on how to contribute to these actions, and contact the action's vendor if you require support for these actions.

App Action Description
Better Excel Automation for Jira Export and email custom Excel spreadsheets from Jira periodically (scheduled reports) or on issue created/updated/etc Generates, exports and emails Excel spreadsheets from Jira issues (available for Automation Lite) Vendor: Midori
Better Excel Exporter for Jira Seamlessly integrate Excel spreadsheet exporting capabilities to your business processes implemented with Jira Creates files in XLSX format compatible with Microsoft Office, Google Spreadsheets, Apple Numbers, Open/Libre Office. Vendor: Midori
Better PDF Exporter for Jira Customizable PDF export for Jira: issue lists, dashboards, timesheets, invoices, Release Notes, story cards & custom documents Exports Jira issues to PDF documents, to share, print, email, archive and report issues in the standard business document file format.  Vendor: Midori
Better PDF Automation for Jira Export, email & save PDF documents from Jira automatically Generates, saves and emails PDF documents from Jira issues. Vendor: Midori
Elements Connect Set nFeed fields value Set an nFeeds field value. Vendor: Elements
ScriptRunner Execute a ScriptRunner script Create and run a groovy script directly in an automation rule! Vendor: Adaptavist
Simple Task lists Add Task Action Automatically add tasks to your task list(s). Vendor: Top Shelf Solutions

Please be aware that third party apps can cause problems with event handling, serialising issues, calculated custom fields, performance issues, etc. Some of the add-ons we've seen cause issues are:

If you experience issues around performance, or rules not running correctly, and you have any of these add-ons installed, try disabling them to see if the problem goes away.

These third party apps have been whitelisted in Lite: