Automation

Previously, automation via webhooks required technical expertise and the use of APIs. We have launched new type of step - ‘Automation step’ which enables us to skip semi-tech steps to set automation. With just a few clicks, we can save your time and reduce human errors by using Automation feature!

You can place the automation step at any place in the approval path. With the automation step at the beginning, you can prepare the issue for the approval process. If placed at the end of the process, you could for example transition the issue to the next phase.

An automation step allows you to perform an action on an issue.

Open

There are five actions available:

Open

• Change issue status - This action changes the status of an issue. The default option is selecting status from a select dropdown listed with corresponding project name or description. Alternatively, you can provide the name of the desired status (case-insensitive). This allows to use same definition for different projects in which they have a status with the same name, e.g. 'Done'. If no status with that name is found within the project, this step will be skipped.

• Change a user assigned to a field - This action changes the user assigned to a field of type user or user list such as Assignee, Creator, Reporter, Request Participants, or Approvers and custom field.

• Add a comment on an issue - Adds a text comment to an issue.

• Add/ remove label(s) - Adds or removes a label on an issue

• Set entity property - Adds an entity property with a specified key and value. You can use issue properties to generate detailed reports on issues that are not covered by Jira's default fields.

To check the entity property, use the following API endpoint:

For more detailed explanations, refer to the Atlassian documentation.