Actions determine the type of field, issue, transition, comment or email processing that should take place.

One or more actions can directly follow a trigger, any condition or any selector. You can add as many actions as needed.


The options actually available depend on which other elements (triggers and/or selectors) have been selected upfront.

Each rule must have at least one action configured before it can be activated!


Automation Toolbox provides the following actions:




Add Comment

Add a new comment to a single issue or multiple issues.

When entering the comment's text, basic and advanced parsing mode are available.

Visibility restrictions can be set for regular issue comments as well as for Jira Service Desk comments.


ParameterDescription
Comment's textEnter comment's text in Basic or Advanced Parsing mode.
Comment's author

Select the author for the comment. It can be chosen from one of the following options:

  • User written to a field, e.g. assignee, reporter
  • Current user
  • Selected user
Comment visibility

Set the visibility of the comment with the following options:

  • Everybody
  • Restricted to Project Role
  • Restricted to Group
  • Jira Service Desk - Public comment
  • Jira Service Desk - Internal comment
Enable email notificationsChoose whether an email notification should be sent according to the applicable notification scheme or not.
Ignore Add Comment permissionWhen selected the Add Comments project permission will be ignored.

The Action has been used in the following examples:



Assign Issue

Assign the issue currently being processed to a specific user or unassign it.


ParameterDescription
Assignee

Select the assignee for the issue. It can be selected from one of the following options:

  • Unassigned
  • Selected User
  • Automatic
  • User in Project Role
Enable email notificationsChoose whether an email notification should be sent according to the applicable notification scheme or not.
Ignore Assign issue permissionWhen selected the Assign Issues project permission will be ignored.
Ignore Assignable User permissionsWhen selected the Assignable User project permissions will be ignored.
Run as

Select the user that will be used to execute the action. It can be chosen from one of the following options:

  • Current user
  • Selected user

The Action has been used in the following examples:



Create Issue

Create one or multiple issues. 

For a more detailed description please see the configuration examples below.


Pro tip

The Create Issue action is the only action allowed for all trigger types.


ParameterDescription
Issues to be created

Select whether one issue or multiple issues should be created. When "Multiple issues" is selected, issue will be created using one of the following options:

  • JQL Query
  • Parser Expression, valid input arguments are String Lists, Issue Lists or Date/Mathematical expressions.
Issue TypeSelect the issue type for the issue(s) that should be created.
Project selection

Select the target project the issues will be created in. It can be chosen from one of the following options:

  • Selected Project
  • Project from Parsed Expression
  • Project from Event, not available for Project, System or Scheduled rules.
  • Project from Issue Selector, this option is available if the action is nested into a selector.
ProjectSelect one or more projects to limit the execution of the rule. If the project selection is empty, the rule is executed every time the event is being fired.
Run as

Select the user that will be used to execute the action. It can be chosen from one of the following options:

  • User written to a field, e.g. assignee, reporter
  • Current user
  • Selected user
Summary

Define the summary for the issue(s) that will be created. It can be chosen between the Basic, Advanced  and Mixed Parsing mode.

DescriptionDefine the description for the issue(s) that will be created. It can be chosen between the Basic, Advanced  and Mixed Parsing mode.
Inherit FieldsInherit field values from other issues, for those fields that have not been set in the following section.
FieldsSet additional values for specific fields.
Inherit Issue LinksInherit issue links from other issues, for those issue links that has not been set in the following section.
Issue LinksSet additional issue links.

The Action has been used in the following examples:



SINCE VERSION 1.1.0

Create an issue link to a single or multiple issues.




Delete Issue

Delete the issue currently being processed.


ParameterDescription
Enable email notificationsChoose whether an email notification should be sent according to the applicable notification scheme or not.
Ignore Delete Issues permissionWhen selected the Delete Issues project permission will be ignored.
Run as

Select the user that will be used to execute the action. It can be chosen from one of the following options:

  • User written to a field, e.g. assignee, reporter
  • Current user
  • Selected user

The Action has been used in the following examples:




SINCE VERSION 1.1.0

Delete issue link(s) to single or multiple issues. The source issue will always be the one currently being processed.




Log Work

SINCE VERSION 1.1.0

Log work to the issue currently being processed.


ParameterDescription
Worklog Author

Select the author for the worklog. It can be chosen from one of the following options:

  • User written to a field, e.g. assignee, reporter
  • Current user
  • Selected user
Remaining estimate adjustments

Select the way the issue's remaining estimate will be adjusted. It can be chosen from the following options:

  • Auto adjustment, the remaining estimate will be adjusted accordingly the entered worklog time.
  • Retain remaining estimate, the remaining estiamte will not be adjusted.
Time to be loggedDefine the worklog duration entered in minutes.
Starting date-timeDefine the worklog's starting date-time.
Work descriptionDefine the comment that should be added to the work log.
Enable email notificationsChoose whether an email notification should be sent according to the applicable notification scheme or not.

The Action has been used in the following examples:





Send Email

Send an email notification.

For a more detailed description please see the configuration examples below.


ParameterDescription
From

Select the sender of the email. It can be chosen from one of the following options:

  • Default, default address configured in the outgoing SMTP mail server configuration
  • Project email address
  • User in field
  • User
  • Email address in field
  • Email address
To/ CC/ Bcc

Select the recipient(s) of the email. Email addresses can be obtained from the following options:

  • Users in field
  • Users
  • Email address in field
  • Project Roles
  • Groups
  • Email addresses (comma separated list)
SubjectDefine the subject for the email(s).
Content Type

Choose the content type of the email(s). It can be chosen between:

  • Text
  • HTML
Priority

Set the email's priority. It can be chosen from:

  • Low
  • Medium
  • High
Sending mode

Select the sending mode of the mail:

  • Common: If there are several recipients, they will get all the same mail. All recipient addresses will be present for everyone if they are entered into the "To" or "Cc" field.
  • Personal: If there are several recipients, everyone will receive a seperate mail.
BodyEnter the mail's body.
Run as

Select the user that will be used to execute the action. It can be chosen from one of the following options:

  • User written to a field, e.g. assignee, reporter
  • Current user
  • Selected user

The Action has been used in the following examples:




Transition Issue

Execute a specific transition on the issue currently being processed or transitions to a selected status.


ParameterDescription
Mode

Select the way the issue should be transitioned. It can be chosen from one of the following options:

  • Transition to status, the first available transition to the target status will be executed.
  • Execute Transition, select any transition from active workflows.
Ignore conditionsWhen selected the conditions for this transition will be ignored.
Ignore validatorsWhen selected the validators for this transition will be ignored.
Ignore permissionsWhen selected the Transition Issues project permission for this transition will be ignored.
Run as

Select the user that will be used to execute the action. It can be chosen from one of the following options:

  • User written to a field, e.g. assignee, reporter
  • Current user
  • Selected user


Update Field

One of the most powerful actions. It can update almost any field to any valid value.


Pro tip

Use the power of the expression parser!


ParameterDescription
Update field configuration

Select the field that should be updated. Based on the selected field it can be chosen from the following options:

  • Selected value that should be set
  • No value - clear field
  • Value returned by parsed expression
Enable email notificationsChoose whether an email notification should be sent according to the applicable notification scheme or not.
Run as

Select the user that will be used to execute the action. It can be chosen from one of the following options:

  • User written to a field, e.g. assignee, reporter
  • Current user
  • Selected user

On this page

  • No labels